| 2.1 |
Approval of the agenda |
|
| R2-2008700 |
Agenda for RAN2#112-e |
Chairman |
| 2.2 |
Approval of the report of the previous meeting |
|
| R2-2008701 |
RAN2#111-e Meeting Report |
MCC |
| 2.4 |
Others |
|
| R2-2010822 |
Correction for LTE CHO and Full Configuration |
R3 (Intel Corporation, Samsung) |
| R2-2010823 |
CHO in stage-2 |
R3 (Ericsson) |
| R2-2010824 |
Corrections on AQP for notification control |
R3 (Ericsson, Nokia, Nokia Shanghai Bell, InterDigital, LG Electronics, Intel Corporation, CATT, ZTE) |
| R2-2010825 |
End marker handling in case of MR-DC NG-RAN initiated QoS Flow offloading |
R3 (Huawei, Deutsche Telekom, Nokia, Nokia Shanghai Bell) |
| R2-2010826 |
End marker handling in case of MR-DC NG-RAN initiated QoS Flow offloading |
R3 (Huawei, Deutsche Telekom, Nokia, Nokia Shanghai Bell) |
| R2-2010827 |
Corrections on AQP for notification control |
R3 (ZTE, Ericsson, Nokia, Nokia Shanghai Bell) |
| R2-2010828 |
Correction on immediate suspension |
R3 (Huawei, Nokia, Nokia Shanghai Bell, Ericsson, Qualcomm Incorporated) |
| R2-2010829 |
Correction of Intra-system HO data forwarding for full configuration |
R3 (Samsung, Intel Corporation, China Telecom, LGU+, Lenovo, Motorola Mobility, Google Inc., CATT, Nokia, Nokia Shanghai Bell) |
| R2-2010830 |
Correction for NR CHO and Full Configuration |
R3 (Intel Corporation, Samsung) |
| R2-2010903 |
End marker handling in case of MR-DC NG-RAN initiated QoS Flow offloading |
R3 (Huawei, Deutsche Telekom, Nokia, Nokia Shanghai Bell) |
| R2-2010988 |
RAN2#112-e Meeting Guidelines |
MCC |
| 3 |
Incoming liaisons |
|
| R2-2008721 |
Reply LS on mandatory support of full rate user plane integrity protection for 5G (R3-205653; contact: Qualcomm) |
RAN3 |
| 4.2 |
eMTC corrections Rel-15 and earlier |
|
| R2-2009723 |
Report of e-mail discussion [Post111-e][922][NB-IoT/eMTC R15] UP EDT for DRB using RLC AM (Huawei) |
Huawei, HiSilicon |
| R2-2009724 |
Clarification to UP-EDT |
Huawei, HiSilicon |
| R2-2009725 |
Clarification to UP-EDT |
Huawei, HiSilicon |
| R2-2009726 |
Clarification to UP-EDT |
Huawei, HiSilicon |
| R2-2009727 |
Clarification to UP-EDT |
Huawei, HiSilicon |
| R2-2009734 |
Addition of cross-TTI MIB/SIB-BR decoding capability |
Huawei, HiSilicon |
| R2-2009735 |
Addition of cross-TTI MIB/SIB-BR decoding capability |
Huawei, HiSilicon |
| R2-2010810 |
Clarification to completion of UP-EDT procedure when using RLC AM |
Huawei, HiSilicon |
| R2-2010811 |
Clarification to completion of UP-EDT procedure when using RLC AM |
Huawei, HiSilicon |
| R2-2010812 |
Clarification to UP-EDT |
Huawei, HiSilicon |
| R2-2010813 |
Clarification to UP-EDT |
Huawei, HiSilicon |
| R2-2010814 |
Addition of cross-TTI MIB/SIB-BR decoding capability |
Huawei, HiSilicon |
| R2-2010815 |
Addition of cross-TTI MIB/SIB-BR decoding capability |
Huawei, HiSilicon |
| R2-2010820 |
Summary of [AT112-e][401][NB-IoT/eMTC R15] UP EDT for DRB using RLC AM (Huawei) |
Huawei, HiSilicon |
| 4.3 |
V2X and Sidelink corrections Rel-15 and earlier |
|
| R2-2008769 |
IEEE 1609 WG Liaison Message to 3GPP regarding defined values for V field in the Release 14 specification of MAC header |
IEEE 1609 WG |
| R2-2009181 |
Corrections on MAC reset regarding SL BSR cancellation |
Ericsson |
| R2-2009213 |
Corrections on MAC reset regarding SL BSR cancellation |
Ericsson |
| R2-2009214 |
Corrections on MAC reset regarding SL BSR cancellation |
Ericsson |
| R2-2009215 |
Corrections on MAC reset regarding SL BSR cancellation |
Ericsson |
| R2-2009216 |
Corrections on MAC reset regarding SL BSR cancellation |
Ericsson |
| R2-2009402 |
Discussion on the IEEE incoming LS on MAC header V field for LTE V2X SL communication |
Huawei, Ericsson, CATT, LG Electronics Inc., Samsung, OPPO, ZTE, Sanechips, HiSilicon |
| R2-2009832 |
UE capability for EUTRA V2X in DC |
vivo |
| R2-2010336 |
Correction on the capability bit v2x-EUTRA of option-1 |
vivo |
| R2-2010337 |
Correction on the capability bit v2x-EUTRA of option-2 |
vivo |
| R2-2010338 |
Correction on the capability bit v2x-EUTRA of option-3 |
vivo |
| R2-2010925 |
Reply LS on defined values for V field in the Release 14 specification of MAC header |
RAN2 |
| R2-2010942 |
[Summary of [AT112-e][701][V2X] Response LS on MAC header V field for LTE V2X SL communication (Huawei) |
Huawei |
| 4.5 |
Other LTE corrections Rel-15 and earlier |
|
| R2-2008901 |
Removal of DelayBudgetReport message in stage 3 |
Lenovo, Motorola Mobility |
| R2-2008902 |
Removal of DelayBudgetReport message in stage 3 |
Lenovo, Motorola Mobility |
| R2-2008903 |
Removal of DelayBudgetReport message in stage 3 |
Lenovo, Motorola Mobility |
| R2-2008904 |
Removal of DelayBudgetReport message in stage 2 |
Lenovo, Motorola Mobility |
| R2-2008905 |
Removal of DelayBudgetReport message in stage 2 |
Lenovo, Motorola Mobility |
| R2-2008906 |
Removal of DelayBudgetReport message in stage 2 |
Lenovo, Motorola Mobility |
| R2-2009257 |
Correction to RRC resume and re-establishment |
Google Inc. |
| R2-2009258 |
Correction to RRC resume and re-establishment |
Google Inc. |
| R2-2009428 |
Clarification to UE capabilities for non-contiguous intra-band CA |
Nokia, Nokia Shanghai Bell, Qualcomm Incorporated |
| R2-2009429 |
Clarification to UE capabilities for non-contiguous intra-band CA |
Nokia, Nokia Shanghai Bell, Qualcomm Incorporated |
| R2-2009430 |
Clarification to UE capabilities for non-contiguous intra-band CA |
Nokia, Nokia Shanghai Bell, Qualcomm Incorporated |
| R2-2009431 |
Clarification to UE capabilities for non-contiguous intra-band CA |
Nokia, Nokia Shanghai Bell, Qualcomm Incorporated |
| R2-2009432 |
Clarification to UE capabilities for non-contiguous intra-band CA |
Nokia, Nokia Shanghai Bell, Qualcomm Incorporated |
| R2-2009565 |
PDCP re-establishment for normal DRBs configured with RLC OOD and ROHC |
Samsung |
| R2-2009566 |
CR on PDCP re-establishment when t-Reordering is used |
Samsung |
| R2-2009567 |
CR on PDCP re-establishment when t-Reordering is used |
Samsung |
| R2-2009568 |
Clarification on ROHC configuration |
Samsung |
| R2-2009569 |
Correction on ROHC configuration |
Samsung |
| R2-2009570 |
Correction on ROHC configuration |
Samsung |
| R2-2009571 |
Correction on lch-CellRestriction |
Samsung |
| R2-2009572 |
Correction on lch-CellRestriction |
Samsung |
| R2-2009763 |
Correction to RRC resume for CIoT |
Google Inc. |
| R2-2009764 |
Correction to RRC resume for CIoT |
Google Inc. |
| R2-2009801 |
Miscellaneous Stage-2 corrections |
Nokia (rapporteur), NEC |
| R2-2009921 |
Corrections to the field descriptions for TDD/FDD capability differentiation |
Huawei, HiSilicon |
| R2-2009922 |
Corrections to the field descriptions for TDD/FDD capability differentiation |
Huawei, HiSilicon |
| R2-2010153 |
Recommended bit rate query handling at MAC Reset |
Ericsson |
| R2-2010154 |
Recommended bit rate query handling at MAC Reset |
Ericsson |
| R2-2010155 |
Recommended bit rate query handling at MAC Reset |
Ericsson |
| R2-2010710 |
Summary of [AT112-e][201][LTE] LTE Miscellaneous corrections (RAN2 VC) |
Nokia (RAN2 VC) |
| R2-2010711 |
Summary of [AT112-e][202][LTE] LTE editorial corrections (RAN2 VC) |
Nokia (RAN2 VC) |
| R2-2010712 |
Miscellaneous Stage-2 corrections |
Nokia (rapporteur), NEC, Lenovo, Motorola Mobility |
| R2-2010714 |
Summary of [AT112-e][203][LTE] LTE corrections related to RLC out-of-order delivery (Samsung) |
Samsung |
| R2-2010735 |
Corrections to the field descriptions for TDD/FDD capability differentiation |
Huawei, HiSilicon |
| R2-2010736 |
Corrections to the field descriptions for TDD/FDD capability differentiation |
Huawei, HiSilicon |
| R2-2010753 |
Addition of missing NZP CSI-RS transmission capabilities |
Huawei, HiSilicon |
| R2-2010754 |
Addition of missing NZP CSI-RS transmission capabilities |
Huawei, HiSilicon |
| R2-2010759 |
Corrections to the field descriptions for TDD/FDD capability differentiation |
Huawei, HiSilicon |
| R2-2010899 |
Corrections to the field descriptions for TDD/FDD capability differentiation, and to nMaxResource value range |
Huawei, HiSilicon |
| R2-2011001 |
Reply LS on Incomplete LTE Physical Layer Capabilities (R1-2009435; contact: Huawei) |
RAN1 |
| R2-2011077 |
Summary of [AT112-e][203][LTE] LTE corrections related to RLC out-of-order delivery (Samsung) |
Samsung |
| R2-2011078 |
Correction on ROHC configuration |
Samsung |
| R2-2011079 |
Correction on ROHC configuration |
Samsung |
| R2-2011080 |
Correction on lch-CellRestriction |
Samsung |
| R2-2011081 |
Correction on lch-CellRestriction |
Samsung |
| R2-2011085 |
Corrections to the field descriptions for TDD/FDD capability differentiation |
Huawei, HiSilicon |
| R2-2011090 |
Clarification to UE capabilities for non-contiguous intra-band CA |
Nokia, Nokia Shanghai Bell, Qualcomm Incorporated |
| R2-2011091 |
Clarification to UE capabilities for non-contiguous intra-band CA |
Nokia, Nokia Shanghai Bell, Qualcomm Incorporated |
| R2-2011092 |
Clarification to UE capabilities for non-contiguous intra-band CA |
Nokia, Nokia Shanghai Bell, Qualcomm Incorporated |
| R2-2011093 |
Clarification to UE capabilities for non-contiguous intra-band CA |
Nokia, Nokia Shanghai Bell, Qualcomm Incorporated |
| R2-2011094 |
Clarification to UE capabilities for non-contiguous intra-band CA |
Nokia, Nokia Shanghai Bell, Qualcomm Incorporated |
| R2-2011250 |
Correction on ROHC configuration |
Samsung |
| R2-2011251 |
Correction on lch-CellRestriction |
Samsung |
| R2-2011256 |
Corrections to the field descriptions for TDD/FDD capability differentiation, and to nMaxResource value range |
Huawei, HiSilicon |
| 5.1 |
Organisational |
|
| R2-2008733 |
Reply LS on UE capability xDD differentiation for SUL/SDL bands (R4-2011687; contact: ZTE) |
RAN4 |
| R2-2011204 |
Reply LS on UE capability xDD differentiation for SUL/SDL bands (R1-2009576; contact: Samsung) |
RAN1 |
| 5.2 |
Stage 2 corrections |
|
| R2-2011036 |
Offline 001 on Stage 2 Corrections |
Nokia (Rapporteur) |
| 5.2.1 |
TS 3x.300 |
|
| R2-2008816 |
Clarification of SCell setup during inter-RAT HO |
Nokia, Nokia Shanghai Bell |
| R2-2008817 |
Clarification of SCell setup during inter-RAT HO |
Nokia, Nokia Shanghai Bell |
| R2-2008818 |
Clarification of SCell setup during inter-RAT HO |
Nokia, Nokia Shanghai Bell |
| R2-2008819 |
Clarification of SCell setup during inter-RAT HO |
Nokia, Nokia Shanghai Bell |
| R2-2008820 |
Clarification of SCell setup during inter-RAT HO |
Nokia, Nokia Shanghai Bell |
| R2-2009308 |
UE Capabilities Description |
Nokia (Rapporteur), Ericsson, Nokia Shanghai Bell, Qualcomm Incorporated, Sanechips, ZTE |
| R2-2009309 |
UE Capabilities Description |
Nokia (Rapporteur), Ericsson, Nokia Shanghai Bell, Qualcomm Incorporated, Sanechips, ZTE |
| R2-2009310 |
Cell Terminology |
Nokia (Rapporteur), Nokia Shanghai Bell, Sanechips, ZTE |
| R2-2009311 |
Cell Terminology |
Nokia (Rapporteur), Nokia Shanghai Bell, Sanechips, ZTE |
| R2-2011034 |
UE Capabilities Description |
Nokia (Rapporteur), Ericsson, Nokia Shanghai Bell, Qualcomm Incorporated, Sanechips, ZTE |
| R2-2011035 |
UE Capabilities Description |
Nokia (Rapporteur), Ericsson, Nokia Shanghai Bell, Qualcomm Incorporated, Sanechips, ZTE |
| 5.2.2 |
TS 37.340 |
|
| R2-2008821 |
UE Capabilities Description |
Nokia, Nokia Shanghai Bell, ZTE Corporation (rapporteur) |
| R2-2008822 |
UE Capabilities Description |
Nokia, Nokia Shanghai Bell, ZTE Corporation (rapporteur) |
| R2-2011127 |
UE Capabilities description |
Nokia, Nokia Shanghai Bell, ZTE Corporation (rapporteur) |
| 5.3.1 |
MAC |
|
| R2-2008909 |
Fixing a CR implementation error of CR0767 |
Lenovo, Motorola Mobility, Samsung (Rapporteur) |
| R2-2009348 |
Clarification on configuredGrantTimer |
Nokia, Nokia Shanghai Bell, Ericsson, LG |
| R2-2009482 |
Clarification on PHR reporting for PUSCH skipping |
Apple |
| R2-2009792 |
Clarification on configured grant (re-)initialization |
Nokia, Nokia Shanghai Bell |
| R2-2009793 |
Clarification on configured grant (re-)initialization |
Nokia, Nokia Shanghai Bell |
| R2-2009910 |
CR on 38.321 for HARQ process handling of retransmission within a bundle-R15 |
ZTE Corporation, Sanechips |
| R2-2009911 |
CR on 38.321 for HARQ process handling of retransmission within a bundle-R16 |
ZTE Corporation, Sanechips |
| R2-2010156 |
Recommended bit rate query handling at MAC Reset |
Ericsson |
| R2-2010157 |
Recommended bit rate query handling at MAC Reset |
Ericsson |
| R2-2010164 |
Consistent use of terminology for bundling in MAC |
Ericsson, Samsung |
| R2-2010165 |
Clarification of timer value zero interpretation in MAC |
Ericsson, Samsung |
| R2-2010166 |
Clarification of timer value zero interpretation in MAC |
Ericsson, Samsung |
| R2-2010318 |
Further discussions on DRX with bundling operation |
Huawei, HiSilicon |
| R2-2010330 |
Clarification on LCP restriction for configured grant type 1 |
MediaTek Inc. |
| R2-2010418 |
Clarification for bundling transmission |
ASUSTeK |
| R2-2010426 |
Correction on DRX with bundle transmission of configured uplink grant |
ASUSTeK |
| R2-2010621 |
Activation of CG and DRX Inactivity Timer |
Ericsson |
| R2-2010622 |
Incorrectly stopping DRX retransmission timer when bundling is used |
Ericsson |
| R2-2010623 |
Incorrectly stopping DRX retransmission timer when bundling is used |
Ericsson |
| R2-2010624 |
Incorrectly stopping DRX retransmission timer when bundling is used |
Ericsson |
| R2-2010679 |
CR on TS 38.331 for LCP restriction of configured grant type 1 |
MediaTek |
| R2-2010680 |
CR on TS 38.331 for LCP restriction of configured grant type 1 |
MediaTek |
| R2-2011032 |
Miscellaneous corrections on bundling operation |
Samsung, Ericsson, Lenovo, Motorola Mobility, ASUSTeK, Nokia |
| R2-2011033 |
Report of [AT112-e][003][NR15] MAC II (Samsung) |
Samsung |
| R2-2011045 |
Correction on DRX with bundle transmission of configured uplink grant |
ASUSTeK, Ericsson, Samsung, Nokia |
| R2-2011105 |
Report of [AT112-e][002][NR15] MAC I (MediaTek) |
MediaTek Inc. |
| R2-2011106 |
CR on TS 38.331 for LCP restriction of configured grant type 1 |
MediaTek |
| R2-2011107 |
CR on TS 38.331 for LCP restriction of configured grant type 1 |
MediaTek |
| R2-2011108 |
Clarification on configured grant (re-)initialization |
Nokia, Nokia Shanghai Bell |
| R2-2011109 |
Clarification on configured grant (re-)initialization |
Nokia, Nokia Shanghai Bell |
| R2-2011155 |
CR on TS 38.331 for LCP restriction of configured grant type 1 |
MediaTek |
| R2-2011156 |
CR on TS 38.331 for LCP restriction of configured grant type 1 |
MediaTek |
| R2-2011282 |
CR on TS 38.331 for LCP restriction of configured grant type 1 |
MediaTek |
| R2-2011283 |
CR on TS 38.331 for LCP restriction of configured grant type 1 |
MediaTek |
| 5.3.3 |
PDCP |
|
| R2-2009481 |
NW configuration on PDCP recovery |
Apple |
| R2-2010559 |
PDCP status report |
Qualcomm Incorporated |
| R2-2010560 |
PDCP status report |
Qualcomm Incorporated |
| R2-2010667 |
Corrections on PDCP functionalities |
Huawei, HiSilicon |
| R2-2010668 |
Corrections on PDCP functionalities |
Huawei, HiSilicon |
| R2-2011126 |
Summary of email discussion [AT112-e][004][NR15] PDCP (Apple) |
Apple |
| 5.4.1 |
NR RRC |
|
| R2-2010859 |
Email discussion report [Post112-e][050][NR15 NR16] |
Ericsson |
| 5.4.1.1 |
Connection control |
|
| R2-2008715 |
LS reply on NR SRS carrier switching (R1-2007395; contact: Qualcomm) |
RAN1 |
| R2-2009183 |
Discussion on SRS carrier switching based on RAN1 reply LS (R1-2007395) |
Qualcomm Incorporated, ZTE Corporation, Sanechips, Ericsson, MediaTek Inc. |
| R2-2009184 |
Correction for configuration of SRS Carrier Switching |
Qualcomm Incorporated, ZTE Corporation, Sanechips, Ericsson, MediaTek Inc. |
| R2-2009185 |
Correction for configuration of SRS Carrier Switching |
Qualcomm Incorporated, ZTE Corporation, Sanechips, Ericsson, MediaTek Inc. |
| R2-2009233 |
Clarify UE behaviour on Need S Need R fields |
ZTE Corporation, Sanechips |
| R2-2009234 |
CR to clarify UE behaviour on Need S Need R fields |
ZTE Corporation, Sanechips |
| R2-2009235 |
CR to clarify UE behaviour on Need S Need R fields |
ZTE Corporation, Sanechips |
| R2-2009236 |
CR to clarify smtc field in case of SCell addition |
ZTE Corporation, Sanechips |
| R2-2009237 |
CR to clarify smtc field in case of SCell addition |
ZTE Corporation, Sanechips |
| R2-2009355 |
Corrections on the configurations of HARQ-ACK spatial bundling and CBG in 38.331 |
CATT |
| R2-2009356 |
Corrections on the configurations of HARQ-ACK spatial bundling and CBG in 38.331 |
CATT |
| R2-2009478 |
Clarification on AS configuration during HO |
Apple |
| R2-2009479 |
Clarification on the SCell RACH configuration |
Apple |
| R2-2009580 |
Correction on rach-ConfigDedicated |
ZTE Corporation, Sanechips |
| R2-2009581 |
Correction on rach-ConfigDedicated(R16) |
ZTE Corporation, Sanechips |
| R2-2009582 |
Correction on essential system information |
ZTE Corporation, Sanechips |
| R2-2009583 |
Correction on essential system information(R16) |
ZTE Corporation, Sanechips |
| R2-2009697 |
Clarification on RRC Reestablishment procedure |
Ericsson |
| R2-2009698 |
Correction on terminology for when the UE is configured with SUL |
Ericsson |
| R2-2009699 |
Correction on terminology for when the UE is configured with SUL |
Ericsson |
| R2-2009844 |
FH configuration for 1-symbol PUCCH |
Ericsson |
| R2-2009845 |
FH configuration for 1-symbol PUCCH |
Ericsson |
| R2-2010492 |
Clarification on the terminology ‘serving cell is configured with a supplementary uplink’ |
Fujitsu |
| R2-2010530 |
clarification on p-Max in FR2 rel-15 |
NTT DOCOMO, INC. |
| R2-2010531 |
Clarification on p-Max in FR2 |
NTT DOCOMO, INC. |
| R2-2010557 |
Allowing Deactivation of SCells for Overheating Mitigation |
Qualcomm Incorporated |
| R2-2010558 |
Allowing Deactivation of SCells for Overheating Mitigation |
Qualcomm Incorporated |
| R2-2010563 |
SRS Resource Set upon PUCCH Release |
Qualcomm Incorporated |
| R2-2010584 |
Clarification on the terminology ‘serving cell is configured with a supplementary uplink’ |
Fujitsu |
| R2-2010665 |
Corrections on configuration of first active BWPs |
Huawei, HiSilicon |
| R2-2010666 |
Corrections on configuration of first active BWPs |
Huawei, HiSilicon |
| R2-2011042 |
Email discussion summary of [005][NR15] RRC Conn Control I |
Qualcomm Incorporated |
| R2-2011043 |
Email discussion summary of [005][NR15] RRC Conn Control II |
Email discussion summary of [005][NR15] RRC Conn Control I |
| R2-2011131 |
Corrections on configuration of first active BWPs |
Huawei, HiSilicon |
| R2-2011132 |
Corrections on configuration of first active BWPs |
Huawei, HiSilicon |
| R2-2011175 |
Email discussion summary of [006][NR15] RRC Conn Control II |
ZTE Corporation |
| R2-2011184 |
Email discussion summary of [005][NR15] RRC Conn Control II |
Email discussion summary of [005][NR15] RRC Conn Control I |
| R2-2011187 |
Email discussion summary of [006][NR15] RRC Conn Control II |
ZTE Corporation |
| R2-2011192 |
Corrections on the configurations of HARQ-ACK spatial bundling and CBG in 38.331 |
CATT |
| R2-2011193 |
Corrections on the configurations of HARQ-ACK spatial bundling and CBG in 38.331 |
CATT |
| R2-2011212 |
Correction for configuration of SRS Carrier Switching |
Qualcomm Incorporated, ZTE Corporation, Sanechips, Ericsson, MediaTek Inc. |
| R2-2011213 |
Correction for configuration of SRS Carrier Switching |
Qualcomm Incorporated, ZTE Corporation, Sanechips, Ericsson, MediaTek Inc. |
| R2-2011252 |
Corrections on configuration of first active BWPs |
Huawei, HiSilicon |
| R2-2011253 |
Corrections on configuration of first active BWPs |
Huawei, HiSilicon |
| 5.4.1.3 |
System information |
|
| R2-2009394 |
Clarification on SIB mapping to SI message |
MediaTek Inc.,Huawei, HiSilicon, Ericsson, Nokia, Nokia Shanghai Bell |
| R2-2009398 |
Clarification on SIB mapping to SI message |
MediaTek Inc., Huawei, HiSilicon, Ericsson, Nokia, Nokia Shanghai Bell |
| R2-2009808 |
Correction on uac-AccessCategory1-SelectionAssistanceInfo |
ZTE corporation, Sanechips, Nokia, Ericsson, CMCC, ChinaTelecom, CATT |
| R2-2009809 |
Correction on uac-AccessCategory1-SelectionAssistanceInfo |
ZTE corporation, Sanechips, Nokia, Ericsson, CMCC, ChinaTelecom, CATT |
| R2-2009810 |
Correction on uac-AC1-SelectAssistInfo |
ZTE corporation, Sanechips, Nokia, Ericsson, CMCC, ChinaTelecom, CATT |
| R2-2009811 |
Correction on uac-AC1-SelectAssistInfo |
ZTE corporation, Sanechips, Nokia, Ericsson, CMCC, ChinaTelecom, CATT |
| R2-2010414 |
Correction on SIB acquisition |
Google Inc. |
| R2-2010436 |
Correction on SIB acquisition |
Google Inc. |
| R2-2010483 |
Correction on uac-AccessCategory1-SelectionAssistanceInfo |
ZTE corporation, Sanechips, Nokia, Ericsson, CMCC, ChinaTelecom, CATT |
| R2-2010484 |
Correction on uac-AccessCategory1-SelectionAssistanceInfo |
ZTE corporation, Sanechips, Nokia, Ericsson, CMCC, ChinaTelecom, CATT |
| R2-2010485 |
Correction on uac-AC1-SelectAssistInfo |
ZTE corporation, Sanechips, Nokia, Ericsson, CMCC, ChinaTelecom, CATT |
| R2-2010486 |
Correction on uac-AC1-SelectAssistInfo |
ZTE corporation, Sanechips, Nokia, Ericsson, CMCC, ChinaTelecom, CATT |
| R2-2010999 |
Correction on uac-AC1-SelectAssistInfo |
ZTE corporation, Sanechips, Nokia, Ericsson, CMCC, ChinaTelecom, CATT |
| R2-2011067 |
Clarification on SIB mapping to SI message |
MediaTek Inc., Huawei, HiSilicon, Ericsson, Nokia, Nokia Shanghai Bell |
| R2-2011068 |
Clarification on SIB mapping to SI message |
MediaTek Inc., Huawei, HiSilicon, Ericsson, Nokia, Nokia Shanghai Bell |
| R2-2011069 |
Report of [AT112-e][007][NR15] System Information and Idle mode (ZTE) |
ZTE Corporation, Sanechips |
| R2-2011070 |
Correction on uac-AccessCategory1-SelectionAssistanceInfo |
ZTE corporation, Sanechips, Nokia, Ericsson, CMCC, ChinaTelecom, CATT |
| R2-2011071 |
Correction on uac-AC1-SelectAssistInfo |
ZTE corporation, Sanechips, Nokia, Ericsson, CMCC, ChinaTelecom, CATT |
| 5.4.1.4 |
Inter-Node RRC messages |
|
| R2-2008717 |
LS response on power sharing for LTE mobility enhancements (R1-2007420; contact: Ericsson) |
RAN1 |
| R2-2008727 |
Band selection and indication on single connectivity (R3-205765; contact: ZTE) |
RAN3 |
| R2-2009159 |
Clarification to usage of MN and SN configuration restrictions |
Nokia, Nokia Shanghai Bell |
| R2-2009160 |
Clarification to usage of MN and SN configuration restrictions |
Nokia, Nokia Shanghai Bell |
| R2-2009161 |
Clarification to usage of MN and SN configuration restrictions |
Nokia, Nokia Shanghai Bell |
| R2-2009242 |
Discussion RAN3 LS on band selection and indication |
ZTE Corporation, Sanechips, Nokia, Nokia Shanghai Bell |
| R2-2009243 |
Reply LS on band selection and indication |
ZTE Corporation, Sanechips |
| R2-2010357 |
Disucssion on overlapping band handling |
Huawei, HiSilicon |
| R2-2010359 |
Clarification on scg-CellGroupConfigEUTRA |
Huawei, HiSilicon |
| R2-2010360 |
Clarification on scg-CellGroupConfigEUTRA |
Huawei, HiSilicon |
| R2-2010542 |
Band selection and indication on single connectivity |
Ericsson |
| R2-2010976 |
Intra-band EN-DC deployment issue |
Nokia, Nokia Shanghai Bell |
| R2-2011028 |
Summary for Offline [008][NR15] inter-node RRC (Huawei) |
Huawei |
| R2-2011029 |
Clarification on scg-CellGroupConfigEUTRA |
Huawei, HiSilicon |
| R2-2011030 |
Clarification on scg-CellGroupConfigEUTRA |
Huawei, HiSilicon |
| R2-2011188 |
Reply LS on band selection and indication |
RAN2 |
| R2-2011224 |
Clarification to usage of MN and SN configuration restrictions |
Nokia, Nokia Shanghai Bell |
| R2-2011225 |
Clarification to usage of MN and SN configuration restrictions |
Nokia, Nokia Shanghai Bell |
| 5.4.1.5 |
Other |
|
| R2-2009074 |
Correction on UAI during handover |
vivo, Ericsson, Xiaomi, Intel Corporation, Huawei, HiSilicon |
| R2-2009075 |
Correction on UAI during handover |
vivo, Ericsson, Xiaomi, Intel Corporation, Huawei, HiSilicon |
| R2-2009076 |
Correction on UAI during handover |
vivo, Ericsson, Xiaomi, Intel Corporation, Huawei, HiSilicon |
| R2-2009077 |
Correction on UAI during handover |
vivo, Ericsson, Xiaomi, Intel Corporation, Huawei, HiSilicon |
| R2-2009078 |
Correction on prohibit timer upon MR-DC release |
vivo |
| R2-2009477 |
Clarification on optional feature without UE AS capability |
Apple |
| R2-2009840 |
Miscellaneous non-controversial corrections Set VIII |
Ericsson |
| R2-2009842 |
Correction to release of list elements using toReleaseList |
Ericsson |
| R2-2009843 |
Correction to release of list elements using toReleaseList |
Ericsson |
| R2-2011145 |
Email discussion report [AT112-e][009][NR15] RRC Misc |
Ericsson |
| R2-2011147 |
Miscellaneous non-controversial corrections Set VIII |
Ericsson |
| R2-2011149 |
Correction to release of list elements using toReleaseList |
Ericsson |
| R2-2011150 |
Correction to release of list elements using toReleaseList |
Ericsson |
| R2-2011254 |
Miscellaneous non-controversial corrections Set VIII |
Ericsson |
| 5.4.2 |
LTE changes related to NR |
|
| R2-2008823 |
Clarification to usage of ul-256QAM-r15 |
Nokia, Nokia Shanghai Bell |
| R2-2008824 |
Clarification to usage of ul-256QAM-r15 |
Nokia, Nokia Shanghai Bell |
| R2-2009946 |
Clarification for the final check on cell selection criterion |
Ericsson, Qualcomm |
| R2-2009950 |
Open issues on SIB extension correction |
Ericsson |
| R2-2010600 |
Correction on p-MaxEUTRA upon SN release |
ZTE Corporation, Sanechips |
| R2-2010601 |
Correction on p-MaxEUTRA upon SN release |
ZTE Corporation, Sanechips |
| R2-2011172 |
Clarification for SIBs scheduled in schedulingInfoListExt and posSchedulingInfoList |
Ericsson, Intel, NTT DOCOMO, INC., Samsung, ZTE Corporation, Sanechips, MediaTek Inc., Qualcomm, T-Mobile USA Inc. |
| R2-2011173 |
Clarification for SIBs scheduled in schedulingInfoListExt and posSchedulingInfoList |
Ericsson, Intel, NTT DOCOMO, INC., Samsung, ZTE Corporation, Sanechips, MediaTek Inc., Qualcomm, T-Mobile USA Inc. |
| R2-2011215 |
Capturing ul-256QAM-r15 capability |
Nokia, Nokia Shanghai Bell |
| R2-2011216 |
Capturing ul-256QAM-r15 capability |
Nokia, Nokia Shanghai Bell |
| R2-2011217 |
Capturing ul-256QAM-r15 capability |
Nokia, Nokia Shanghai Bell |
| R2-2011218 |
Capturing ul-256QAM-r15 capability |
Nokia, Nokia Shanghai Bell |
| R2-2011227 |
Summary of [AT112-e][010][NR15] LTE changes (Nokia) |
Nokia, Nokia Shanghai Bell |
| R2-2011247 |
Clarification for SIBs scheduled in schedulingInfoListExt and posSchedulingInfoList |
Ericsson, Intel, NTT DOCOMO, INC., Samsung, ZTE Corporation, Sanechips, MediaTek Inc., Qualcomm, T-Mobile USA Inc., Apple, Verizon, Deutsche Telekom, Nokia, Nokia Shanghai Bell, Huawei, HiSilicon |
| R2-2011248 |
Clarification for SIBs scheduled in schedulingInfoListExt and posSchedulingInfoList |
Ericsson, Intel, NTT DOCOMO, INC., Samsung, ZTE Corporation, Sanechips, MediaTek Inc., Qualcomm, T-Mobile USA Inc., Apple, Verizon, Deutsche Telekom, Nokia, Nokia Shanghai Bell, Huawei, HiSilicon |
| 5.4.3 |
UE capabilities and Capability Coordination |
|
| R2-2008710 |
LS on Interpretation of UE Features in Case of Cross-Carrier Operation (R1-2007334; contact: ZTE) |
RAN1 |
| R2-2008734 |
Reply LS on Clarification on RAN4 features of NE-DC (R4-2011688; contact: Samsung) |
RAN4 |
| R2-2008770 |
Correction for RAN4 features of NE-DC |
OPPO, Qualcomm Incorporated |
| R2-2008771 |
Correction for RAN4 features of NE-DC |
OPPO, Qualcomm Incorporated |
| R2-2009162 |
Correction to BWP capabiltiy descriptions |
Nokia, Nokia Shanghai Bell |
| R2-2009163 |
Correction to BWP capabiltiy descriptions |
Nokia, Nokia Shanghai Bell |
| R2-2009238 |
CR to clarify UE capability in case of cross-carrier operation |
ZTE Corporation, Sanechips, Ericsson |
| R2-2009239 |
CR to clarify UE capability in case of cross-carrier operation |
ZTE Corporation, Sanechips, Ericsson |
| R2-2009392 |
Corrections on PDCP duplication capability for NR-DC |
Huawei, HiSilicon |
| R2-2009393 |
Corrections on PDCP duplication capability for NR-DC |
Huawei, HiSilicon |
| R2-2009480 |
Clarification on the capability of supportedNumberTAG |
Apple |
| R2-2009516 |
Correction of the description of ue-SpecificUL-DL-Assignment |
Apple |
| R2-2009517 |
Correction of the description of ue-SpecificUL-DL-Assignment |
Apple |
| R2-2009630 |
Further Consideration on the non-CA BC Capability Reporting |
ZTE Corporation, Sanechips |
| R2-2009944 |
UE capability and cross-slot scheduling for Paging |
Ericsson |
| R2-2010084 |
Internode coordination for superset BCs reported by UE |
Samsung Telecommunications |
| R2-2010238 |
Discussion on band for redirection and measurement configuration |
Huawei, HiSilicon, Ericsson |
| R2-2010239 |
Clarification on the inter-frequency handover capability |
Huawei, HiSilicon, Ericsson |
| R2-2010240 |
Clarification on the inter-frequency handover capability |
Huawei, HiSilicon, Ericsson |
| R2-2010241 |
Clarification on NE-DC for bandwidth combination set |
Huawei, HiSilicon, Samsung |
| R2-2010242 |
Clarification on NE-DC for bandwidth combination set |
Huawei, HiSilicon, Samsung |
| R2-2010512 |
Clarified meaning of band combinations |
Ericsson, Huawei, HiSilicon |
| R2-2010513 |
Clarified meaning of band combinations |
Ericsson, Huawei, HiSilicon |
| R2-2010517 |
Removing contradiction on number of FSpUCC and FSpDCC |
Ericsson, Nokia, Nokia Shanghai-Bell |
| R2-2010518 |
Removing contradiction on number of FSpUCC and FSpDCC |
Ericsson, Nokia, Nokia Shanghai-Bell |
| R2-2010519 |
Removing contradiction on number of FSpUCC and FSpDCC |
Ericsson, Nokia, Nokia Shanghai-Bell |
| R2-2010520 |
Removing contradiction on number of FSpUCC and FSpDCC |
Ericsson, Nokia, Nokia Shanghai-Bell |
| R2-2010536 |
Correction to the use of simultaneous CSI-RS resources |
Ericsson |
| R2-2010537 |
Correction to the use of simultaneous CSI-RS resources |
Ericsson |
| R2-2010538 |
Definition of fallback per CC feature set |
Ericsson |
| R2-2010539 |
Definition of fallback per CC feature set |
Ericsson |
| R2-2010540 |
Correction to pdcch-MonitoringSingleOccasion |
Ericsson |
| R2-2010541 |
Correction to pdcch-MonitoringSingleOccasion |
Ericsson |
| R2-2010545 |
Clarification on UE capabilities with FDD/TDD differentiation |
Ericsson, ZTE Corporation, Sanechips |
| R2-2010546 |
Clarification on UE capabilities with FDD/TDD differentiation |
Ericsson, ZTE Corporation, Sanechips |
| R2-2010561 |
slotAgrregationULConfigGrant capabilities enhancement |
Qualcomm Incorporated |
| R2-2010562 |
slotAgrregationULConfigGrant capabilities enhancement |
Qualcomm Incorporated |
| R2-2010567 |
CR on the non-CA BC Capability Reporting |
ZTE Corporation, Sanechips |
| R2-2010568 |
CR on the non-CA BC Capability Reporting |
ZTE Corporation, Sanechips |
| R2-2010848 |
Clarification on the inter-frequency handover capability |
Huawei, HiSilicon, Ericsson |
| R2-2010849 |
Clarification on the inter-frequency handover capability |
Huawei, HiSilicon, Ericsson |
| R2-2010857 |
Corrections on PDCP duplication capability for NR-DC |
Huawei, HiSilicon |
| R2-2010858 |
Corrections on PDCP duplication capability for NR-DC |
Huawei, HiSilicon |
| R2-2011044 |
Clarification on BWCS for inter-ENDC BC with intra-ENDC band combination |
Bell Mobility, Telus, Nokia, Nokia Shanghai Bell |
| R2-2011082 |
Removing contradiction on number of FSpUCC and FSpDCC |
Ericsson, Nokia, Nokia Shanghai-Bell |
| R2-2011083 |
Removing contradiction on number of FSpUCC and FSpDCC |
Ericsson, Nokia, Nokia Shanghai-Bell |
| R2-2011084 |
Summary of [AT112-e][011][NR15] UE caps I |
Ericsson |
| R2-2011122 |
LS on Interpretation of UE Features in Case of Cross-Carrier Operation (R1-2009623; contact: ZTE) |
RAN1 |
| R2-2011139 |
Summary of offline 013 Rel-15 UE caps III |
Huawei, HiSilicon |
| R2-2011177 |
CR to clarify UE capability in case of cross-carrier operation and Miscellaneous corrections |
ZTE Corporation, Sanechips, Ericsson |
| R2-2011178 |
CR to clarify UE capability in case of cross-carrier operation and Miscellaneous corrections |
ZTE Corporation, Sanechips, Ericsson |
| R2-2011189 |
Summary of [AT112-e][012][NR15] UE caps II |
ZTE Corporation |
| R2-2011260 |
CR to clarify UE capability in case of Cross-Carrier operation |
ZTE Corporation, Sanechips, Ericsson |
| R2-2011261 |
CR to clarify UE capability in case of Cross-Carrier operation |
ZTE Corporation, Sanechips, Ericsson |
| R2-2011274 |
LS on the use of simultaneous CSI-RS resources and ports |
RAN2 |
| 5.4.4 |
Idle/inactive mode procedures |
|
| R2-2009782 |
Clarifications for Inter-RAT Cell Reselection and Mobility State |
MediaTek Inc. |
| 5.5 |
Positioning corrections |
|
| R2-2010138 |
Corrections to E-CID positioning |
Nokia, Nokia Shanghai Bell |
| R2-2010274 |
Correction on OTDOA Positioning support in R15 |
Huawei, HiSilicon |
| R2-2010275 |
Correction to OTDOA Positioning descriptions in R16 |
Huawei, HiSilicon |
| R2-2010569 |
Correction of A-GNSS Periodical retrival of Assistance Data |
Ericsson |
| R2-2010570 |
Correction of A-GNSS Periodical retrival of Assistance Data |
Ericsson |
| R2-2010571 |
Correction of hanging ASN.1 code after END |
Ericsson |
| R2-2010572 |
Correction of hanging ASN.1 code after END |
Ericsson |
| R2-2010860 |
Correction of hanging ASN.1 code after END |
Ericsson |
| R2-2010874 |
Correction on OTDOA Positioning support in R15 |
Huawei, HiSilicon |
| R2-2011076 |
Offline-613 Discussion on LPP transport without signalling access |
Huawei, HiSilicon |
| R2-2011277 |
Correction of hanging ASN.1 code after END |
Ericsson |
| R2-2011278 |
Correction of hanging ASN.1 code after END |
Ericsson |
| R2-2011280 |
Correction on OTDOA Positioning support in R15 |
Huawei, HiSilicon |
| 6.1.1 |
General RRC corrections |
|
| R2-2009101 |
Corrections to SI acquisition in RRC_CONNECTED |
Samsung Electronics Co., Ltd |
| R2-2009102 |
Corrections to SI acquisition in IDLE_INACTIVE |
Samsung Electronics Co., Ltd |
| R2-2009416 |
Miscellaneous corrections to 38.331 on UE configuration release |
ZTE Corporation, Sanechips |
| R2-2009838 |
NR RAN1 Rel-16 ASN.1 consolidated parameter list |
Ericsson |
| R2-2009839 |
Draft Reply LS on updated Rel-16 LTE and NR parameter lists |
Ericsson |
| R2-2009841 |
Miscellaneous non-controversial corrections Set VIII |
Ericsson |
| R2-2009945 |
Clarifications for the common search space on the active BWP |
Ericsson |
| R2-2009976 |
Summary of email discussion [Post111-e][901] Extension scenarios for ToAddMod lists (MediaTek) |
MediaTek Inc. |
| R2-2009982 |
ASN.1 guidelines for extension of ToAddMod/ToRelease lists, and related updates of existing field names |
MediaTek Inc. |
| R2-2009983 |
ToRelease list extensions: unresolved issue from [Post111-e][901] Extension scenarios for ToAddMod lists (MediaTek) |
MediaTek Inc. |
| R2-2010493 |
Clarification on the terminology ‘serving cell is configured with a supplementary uplink’ |
Fujitsu |
| R2-2010685 |
NR RAN1 Rel-16 ASN.1 consolidated parameter list |
Ericsson |
| R2-2010998 |
Miscellaneous corrections to 38.331 on UE configuration release |
ZTE Corporation, Sanechips |
| R2-2011031 |
Draft Reply LS on updated Rel-16 LTE and NR parameter lists |
Ericsson |
| R2-2011037 |
Reply LS on updated Rel-16 LTE and NR parameter lists |
RAN2 |
| R2-2011038 |
Summary of [AT112-e][039][NR16] SI acquisition |
Ericsson |
| R2-2011057 |
Reply LS on updated Rel-16 LTE and NR parameter lists |
RAN2 |
| R2-2011146 |
Email discussion report [AT112-e][014][NR16] RRC general |
Ericsson |
| R2-2011148 |
Miscellaneous non-controversial corrections Set VIII |
Ericsson |
| R2-2011219 |
Clarifications for the common search space on the active BWP |
Ericsson |
| R2-2011255 |
Miscellaneous non-controversial corrections Set VIII |
Ericsson |
| 6.1.2 |
NR Feature Lists and UE capabilities |
|
| R2-2008708 |
LS on updated Rel-16 RAN1 UE features lists for NR (R1-2007327; contact: NTT DoCoMo, AT&T) |
RAN1 |
| R2-2008738 |
LS on FR1 intra-band UL CA UE capability (R4-2011724; contact: Huawei) |
RAN4 |
| R2-2008739 |
LS on UE capability for FR2 inter-band CA (R4-2011741; contact: Nokia) |
RAN4 |
| R2-2009277 |
Miscellaneous corrections for Rel-16 UE capabilities |
Intel Corporation |
| R2-2009278 |
Release-16 UE capabilities based on RAN1, RAN4 feature lists and RAN2 corrections |
Intel Corporation |
| R2-2009279 |
Release-16 UE capabilities based on RAN1, RAN4 feature lists and RAN2 corrections |
Intel Corporation |
| R2-2009280 |
Capturing R1, R2 and R4 feature lists |
Intel Corporation, ZTE Corporation, Sanechips |
| R2-2009306 |
DC location information reporting |
Intel Corporation |
| R2-2009307 |
Discussion on RAN4 FG 7-3b |
Intel Corporation |
| R2-2009819 |
Correction to skipUplinkTxDynamic |
vivo |
| R2-2009824 |
Discussion on new UE capability of dynamic UL skipping in Rel-16 |
vivo, Nokia, Nokia Shanghai Bell, Xiaomi |
| R2-2009846 |
UE capability for configuration of SMTC of target SCG cell |
Ericsson |
| R2-2009847 |
UE capability for configuration of SMTC of target SCG cell |
Ericsson |
| R2-2010049 |
Out-of-order CBG-based re-transmission(s) with cancelled initial PUSCH transmission |
Ericsson |
| R2-2010050 |
Correction for SPS capability |
Ericsson |
| R2-2010851 |
Release-16 UE capabilities based on RAN1, RAN4 feature lists and RAN2 corrections |
Intel Corporation |
| R2-2010852 |
Release-16 UE capabilities based on RAN1, RAN4 feature lists and RAN2 |
Intel Corporation |
| R2-2010853 |
Update the deployment scenarios in Annex B.3 |
Intel Corporation |
| R2-2010993 |
Corrections for drx-Adaptation capability |
Ericsson |
| R2-2011023 |
Reply LS on FR1 intra-band UL CA UE capability |
RAN2 |
| R2-2011024 |
[AT112-e][015][NR16] UE capabilities (Intel) |
Intel Corporation |
| R2-2011039 |
Summary on [AT112-e][046][NR16] Out-of-order CBG-based re-transmission |
Ericsson |
| R2-2011120 |
LS on updated Rel-16 RAN1 UE features lists for NR (R1-2009586; contact: NTT DOCOMO, AT&T) |
RAN1 |
| R2-2011202 |
Reply LS to RAN2 on beamSwitchTiming (R1-2009496; contact: vivo) |
RAN1 |
| R2-2011220 |
Out-of-order CBG-based re-transmission |
Ericsson |
| R2-2011221 |
Out-of-order CBG-based re-transmission |
Ericsson |
| 6.1.3 |
Other |
|
| R2-2008711 |
LS on PUSCH with UL skipping (R1-2007338; contact: vivo) |
RAN1 |
| R2-2008862 |
Correction on dynamic PUSCH skipping when PUCCH with UCI overlaps with PUSCH |
CATT |
| R2-2009484 |
RAN2 Impact on UL skipping enhancement |
Apple |
| R2-2009485 |
MAC CR on UL skipping enhancement |
Apple |
| R2-2009486 |
RRC CR on UL skipping enhancement |
Apple |
| R2-2009487 |
UE capability on UL skipping enhancement |
Apple |
| R2-2009663 |
Corrections to NR UE capabilities and features |
Lenovo, Motorola Mobility |
| R2-2009813 |
Correction to UL skipping of dynamic UL grant |
vivo, Nokia, Nokia Shanghai Bell, Xiaomi |
| R2-2009951 |
Corrections for drx-Adaptation capability |
Ericsson |
| R2-2010051 |
PUSCH with UL skipping |
Ericsson |
| R2-2010162 |
Alignment of SR clause |
Ericsson, Samsung, LG Electronics |
| R2-2010317 |
Discussions on the remaining issues on PUSCH with UL skipping |
Huawei, HiSilicon |
| R2-2010565 |
Draft reply LS on PUSCH with UL skipping |
vivo |
| R2-2011136 |
Report of [AT112-e][016][NR16] Dyn UL skip and other |
vivo |
| R2-2011137 |
Alignment of SR clause |
Ericsson, Samsung, LG Electronics, Nokia |
| 6.2.1 |
General and Stage-2 Corrections |
|
| R2-2009321 |
CR to 37.340 on SRB3 description |
vivo |
| R2-2010151 |
Clarification to BAP routing ID handling |
Ericsson |
| R2-2010351 |
Corrections on non DRB operation for IAB-MT |
Huawei, HiSilicon |
| R2-2011008 |
Summary of [AT112-e][017][IAB] Stage-2 |
Huawei, HiSilicon |
| R2-2011053 |
Corrections on non DRB operation for IAB-MT |
Huawei, HiSilicon |
| 6.2.2 |
BAP Corrections |
|
| R2-2009178 |
BAP behaviour at RLF |
Samsung Electronics GmbH |
| R2-2009662 |
The case of traffic of child nodes of a migrating node |
Samsung, ZTE, Nokia, Nokia Shanghai Bell |
| R2-2009748 |
Miscellaneous corrections to 38.340 for IAB |
Huawei, HiSilicon, Ericsson |
| R2-2009927 |
Handling descendant node traffic at HO |
Samsung, ZTE |
| R2-2011052 |
Miscellaneous corrections to 38.340 for IAB |
Huawei, HiSilicon, Ericsson, Samsung, Nokia, Nokia Shanghai Bell |
| R2-2011059 |
Discussion summary - [AT112-e][018][IAB] BAP |
Samsung |
| 6.2.3 |
User plane Corrections |
|
| R2-2009324 |
CR to 38.322 on Backhaul RLC Channel |
vivo |
| R2-2009745 |
Correction on Tdelta |
Huawei, HiSilicon, Ericsson, Samsung |
| R2-2010150 |
Pre-emptive BSR handling at MAC Reset |
Ericsson |
| R2-2010152 |
Correction to tDelta |
Ericsson |
| R2-2010419 |
Correction on the condition check in Pre-emptive BSR procedure |
ASUSTeK |
| R2-2010684 |
Summary of Rel-16 IAB UP issues and corrections |
Samsung |
| R2-2011054 |
Correction on Tdelta |
Huawei, HiSilicon, Ericsson, Samsung |
| R2-2011123 |
CR to 38.322 on Backhaul RLC Channel |
vivo, Ericsson |
| R2-2011130 |
Summary of [AT112-e][037][IAB] User Plane (Ericsson) |
Ericsson |
| 6.2.4 |
RRC Corrections |
|
| R2-2009005 |
Correction on RRC function description for IAB |
Fujitsu |
| R2-2009322 |
Miscellaneous corrections to TS 36.331 for IAB |
vivo |
| R2-2009323 |
Miscellaneous corrections to TS 38.331 for IAB |
vivo |
| R2-2009390 |
CR for TS38.331 on RLF cause for IAB BH RLF |
ZTE, Sanechips |
| R2-2009746 |
Correction on non-DRB for IAB-MT |
Huawei, HiSilicon |
| R2-2009747 |
Correction on configuration of availabilityIndicator |
Huawei, HiSilicon |
| R2-2009749 |
Corrections on BH RLC bearer |
Huawei, HiSilicon |
| R2-2009750 |
Corrections on intra-donor CU RLF recovery and RLF cause determination |
Huawei, HiSilicon |
| R2-2010149 |
RRC Miscellaneous Corrections |
Ericsson, Huawei, HiSilicon |
| R2-2010230 |
Support of Rel-16 features for SCG in EN-DC |
Huawei, HiSilicon |
| R2-2010602 |
Cause value due to the reception of BH RLF indication |
Lenovo, Motorola Mobility |
| R2-2010635 |
Transmission suspension on BH RLC channel upon IAB-MT failure |
Samsung |
| R2-2010638 |
Miscellaneous corrections for IAB |
Samsung R&D Institute UK |
| R2-2011009 |
Summary of [AT112-e][019][IAB] NR RRC 38331 |
Huawei, HiSilicon |
| R2-2011048 |
Corrections on RLF cause determination |
Huawei, HiSilicon, ZTE, Sanechips, Lenovo, Motorola Mobility |
| R2-2011049 |
Corrections on BH RLC channel |
Huawei, HiSilicon |
| R2-2011050 |
Correction on non-DRB for IAB-MT |
Huawei, HiSilicon |
| R2-2011115 |
RRC Miscellaneous Corrections |
Ericsson, Huawei, HiSilicon, vivo, Samsung, Fujitsu |
| R2-2011179 |
Miscellaneous corrections to TS 36.331 for IAB |
vivo |
| R2-2011180 |
Report of [AT112-e][020][IAB] LTE RRC 36331 (vivo)” |
vivo |
| 6.2.5 |
UE capabilities |
|
| R2-2008954 |
Discussion on the Issues from RAN4 LS on IAB-MT Feature List |
CATT |
| R2-2009417 |
Clarification on IAB-MT capability for Multiple NS |
Nokia, Nokia Shanghai Bell |
| R2-2009418 |
Clarification on Multiple NS and Pmax applicability to IAB-MT |
Nokia, Nokia Shanghai Bell |
| R2-2010352 |
Corrections based on RAN4 LS about IAB-MT feature |
Huawei, HiSilicon |
| R2-2010353 |
Corrections based on RAN4 LS about IAB-MT feature |
Huawei, HiSilicon |
| R2-2011002 |
Summary of IAB UE capabilities under AI 6.2.5 |
Nokia, Nokia Shanghai Bell |
| R2-2011003 |
Summary on [AT112-e][021][IAB] UE capabilities (Nokia) |
Nokia, Nokia Shanghai Bell |
| R2-2011019 |
Draft Reply on IAB-MT feature list |
Nokia |
| R2-2011020 |
Clarification on Power class, Multiple NS and Pmax applicability to IAB-MT |
Nokia, Nokia Shanghai Bell, Huawei |
| R2-2011021 |
Clarification on Multiple NS and Pmax applicability to IAB-MT |
Nokia, Nokia Shanghai Bell |
| R2-2011273 |
Reply LS on IAB-MT feature list |
RAN2 |
| 6.3.1 |
General and Stage-2 Corrections |
|
| R2-2008702 |
LS on UE behavior for P/SP-CSI-RS reception in NR-U (R1-2006195; contact: MediaTek) |
RAN1 |
| R2-2008718 |
Reply LS on UE declaring beam failure due to LBT failures during active TCI switching (R1-2007424; contact: Nokia) |
RAN1 |
| R2-2008743 |
LS reply to RAN1on UE capability on wideband carrier operation for NR-U (R4-2011931; contact: MediaTek) |
RAN4 |
| R2-2009560 |
Miscellaneous corrections for NR-U |
Qualcomm Incorporated |
| R2-2010399 |
Discussion on NR-U capabilities |
Qualcomm Incorporated |
| R2-2010831 |
Miscellaneous corrections for NR-U |
Qualcomm (Rapporteur), Ericsson, Huawei, Nokia, ZTE Corporation |
| R2-2010834 |
[AT112-e][507][NR-U] Large RAR window capability update |
Qualcomm Incorporated |
| R2-2010845 |
LS on capability for extended RAR window monitoring |
RAN2 |
| R2-2010847 |
Name change of the UE capability for the extended RAR window monitoring |
Qualcomm (Rapporteur) |
| R2-2011000 |
Reply LS on UE capability on wideband carrier operation for NR-U (R1-2009385; contact: MediaTek) |
RAN1 |
| 6.3.2 |
User plane |
|
| R2-2008858 |
Corrections on autonomous retransmissions |
CATT |
| R2-2009297 |
Correction on early termination for repetitions |
Huawei, HiSilicon |
| R2-2009298 |
Correction on autonomous retransmission for NR-U |
Huawei, HiSilicon |
| R2-2009300 |
Correction to NDI toggling for Configured Grant for NRU |
Huawei, HiSilicon |
| R2-2010136 |
Clarification of PUCCH resource usage in NR-U |
Qualcomm Incorporated |
| R2-2010163 |
Correction of HARQ operation for NR-U |
Ericsson |
| R2-2010420 |
Clarification for bundling transmission |
ASUSTek |
| R2-2010440 |
Consideration on multiple CG with HARQ sharing |
LG Electronics UK |
| R2-2010840 |
MAC corrections for NR operating in shared spectrum channel access |
Ericsson, CATT, Huawei, Qualcomm |
| 6.3.3 |
Control plane |
|
| R2-2009194 |
Editorial Corrections in RRC for NR-U |
ZTE Corporation, Sanechips |
| R2-2009195 |
Correction to NR-U Energy Detection Threshold configuration |
ZTE Corporation, Sanechips |
| R2-2009295 |
Correction on description for extendedRAR-window |
Huawei, HiSilicon |
| R2-2009296 |
Correction of field description for ra-ResponseWindow |
Huawei, HiSilicon, Ericsson |
| R2-2009299 |
Correction on ssb-SubcarrierOffset in MIB |
Huawei, HiSilicon, Ericsson |
| R2-2009349 |
Clarification on HARQ process sharing for CGs |
Nokia, Nokia Shanghai Bell |
| R2-2009545 |
UE expects clarification |
Nokia, Nokia Shanghai Bell |
| R2-2009546 |
RMTC measurement timing |
Nokia, Nokia Shanghai Bell |
| R2-2009602 |
Corrections on cg-RetransmissionTimer |
Lenovo, Motorola Mobility, LG Electronics |
| R2-2009999 |
Miscellaneous corrections |
Ericsson |
| R2-2010000 |
Correction on csi-RS-ValidationWithDCI |
Ericsson |
| R2-2010001 |
Correction to search space switching config |
Ericsson |
| R2-2010002 |
Correction on freqMonitorLocations |
Ericsson |
| R2-2010835 |
Correction to NR-U Energy Detection Threshold configuration |
ZTE Corporation, Sanechips |
| R2-2010843 |
Report of [AT112e][508][NRU] on Miscellaneous RRC corrections |
Qualcomm Incorporated |
| R2-2010846 |
Report of [AT112e][508][NRU] on Miscellaneous RRC corrections |
Qualcomm Incorporated |
| R2-2011174 |
Correction on description for extendedRAR-window |
Huawei, HiSilicon |
| R2-2011272 |
Correction on description for extendedRAR-window |
Huawei, HiSilicon |
| R2-2011276 |
Correction on description for extendedRAR-Window |
Huawei, HiSilicon, Nokia, Nokia Shanghai-Bell |
| 6.4.1 |
General and Stage-2 corrections |
|
| R2-2008712 |
Reply LS on UE capability (R1-2007339; contact: Oppo) |
RAN1 |
| R2-2008713 |
Reply LS on maximum data rate for NR sidelink (R1-2007353; contact: Samsung) |
RAN1 |
| R2-2008714 |
Reply LS to RAN2 on physical layer related agreements (R1-2007389; contact: Intel) |
RAN1 |
| R2-2008735 |
LS on definition of NR V2X con-current operation (R4-2011713; contact: Huawei) |
RAN4 |
| R2-2008757 |
LS on Tx Profile for NR PC5 (S2-2006191; contact: LGE) |
SA2 |
| R2-2008790 |
[Draft] Reply LS on maximum data rate for NR sidelink |
OPPO |
| R2-2008941 |
Draft LS to RAN1 on in-device coexistence operation |
LG Electronics France |
| R2-2009251 |
[DRAFT] LS on RAN1 agreement on pre-emption |
LG Electronics France |
| R2-2009404 |
Correction on V2X functions in TS 38.300 |
Huawei, HiSilicon |
| R2-2009408 |
On the need of Tx profile for Rel-16 NR sidelink communication |
Huawei, HiSilicon |
| R2-2009409 |
[Draft] Reply LS on TX profile for NR PC5 |
Huawei, HiSilicon |
| R2-2009410 |
[Draft] Reply LS on definition of NR V2X con-current operation |
Huawei, HiSilicon |
| R2-2009825 |
Stage-2 corrections on 38.300 |
vivo |
| R2-2010185 |
Correction for NR SL communication |
Samsung Electronics |
| R2-2010687 |
Reply LS on the re-keying procedure for NR SL (C1-206576; contact: CATT) |
CT1 |
| R2-2010926 |
Reply LS on maximum data rate for NR sidelink |
RAN2 |
| R2-2010927 |
Reply LS on definition of NR V2X con-current operation |
RAN2 |
| R2-2010928 |
Reply LS on TX profile for NR PC5 |
RAN2 |
| R2-2010929 |
Stage-2 corrections for NR sidelink communication |
Samsung Electronics |
| R2-2010930 |
LS on RAN1 agreement on pre-emption |
RAN2 |
| R2-2011015 |
LS reply on SL CG handling(R1-2009460; contact: Ericsson) |
RAN1 |
| R2-2011016 |
LS on R16 V2X Mode-2 agreements to capture in MAC specification (R1-2009474; contact: Intel) |
RAN1 |
| R2-2011017 |
LS reply on RAN2 agreements and RAN1 related issues (R1-2009475; contact: Intel) |
RAN1 |
| R2-2011117 |
Reply LS on definition of NR V2X con-current operation (R1-2009491; contact: Huawei) |
RAN1 |
| R2-2011119 |
LS on configurable values for sl-DCI-ToSL-Trans (R1-2009577; contact: Ericsson) |
RAN1 |
| R2-2011205 |
Reply LS on UE capability for V2X (R1-2009635; contact: OPPO) |
RAN1 |
| R2-2011206 |
Reply LS on maximum data rate for NR sidelink (R1-2009643; contact: OPPO) |
RAN1 |
| 6.4.2 |
Control plane corrections |
|
| R2-2008784 |
Correction on value range of sl-NumSSB-WithinPeriod |
OPPO |
| R2-2008875 |
Discussion on left issue of 38.304 and 36.304 |
CATT |
| R2-2008876 |
Correction to TS 38.304 |
CATT |
| R2-2008877 |
Correction to TS 36.304 |
CATT |
| R2-2008878 |
Clarification on the description of sl-AssistanceConfigNR |
CATT |
| R2-2008942 |
Discussion on synchronization procedure under in-device coexistence operation |
LG Electronics France |
| R2-2009049 |
Corrections on sl-TimeResource in TS 38.331 |
ZTE Corporation, Sanechips |
| R2-2009053 |
CR on TS 38.331 for slot interval between neighboring sidelink SSBs |
ZTE Corporation, Sanechips |
| R2-2009100 |
DAPS HO and NR Sidelink Communication |
Samsung Electronics Co., Ltd |
| R2-2009317 |
Addition of the E-UTRA ARFCN in crossRAT SL |
SHARP Corporation |
| R2-2009403 |
Correction on the definition of RLC-ParametersSidelink-r16 |
Huawei, HiSilicon |
| R2-2009405 |
Clarification on the SL measurement configuration update |
Huawei, HiSilicon |
| R2-2009406 |
Correction on SDAP related procedures and configurations in TS 38.331 |
Huawei, HiSilicon |
| R2-2009407 |
CR on L1 parameters for NR sidelink communication |
Huawei, HiSilicon |
| R2-2009520 |
Correction on Stored Sidelink Measurement Configuration |
Apple, Ericsson |
| R2-2009664 |
Corrections to NR V2X and Sidelink |
Lenovo, Motorola Mobility |
| R2-2009676 |
Left issue on inter-frequency operation for NR-V2X |
OPPO |
| R2-2009702 |
Correction on protection information for sidelink messages |
Ericsson |
| R2-2009703 |
Correction on operations of sidelink DRB release, addition, and modification |
Ericsson |
| R2-2009704 |
Missing value for sl-DCI-ToSL-Trans |
Ericsson |
| R2-2009705 |
Correction on S-SSB periodicity values |
Ericsson |
| R2-2009706 |
Missing sidelink-related field descriptions |
Ericsson |
| R2-2009709 |
Adding protection information for sidelink messages |
Ericsson |
| R2-2009710 |
Missing SidelinkUEInformation in processing delay requirements |
Ericsson |
| R2-2009711 |
Correction on setting of sl-FailureList in SidelinkUEInformation |
Ericsson |
| R2-2009712 |
Corrections to sidelink radio link failure |
Ericsson |
| R2-2009713 |
Correction on sidelink reset configuration |
Ericsson |
| R2-2009714 |
Correction on conditions for sidelink DRB release |
Ericsson |
| R2-2009715 |
Correction to transmission of MasterInformationBlockSidelink |
Ericsson |
| R2-2009718 |
Correction to the setting of empty SL RRC messages |
Ericsson |
| R2-2009778 |
Correction to UEAssistanceInformation for sidelink communication |
Google Inc. |
| R2-2009826 |
Miscellaneous corrections to 38.331 on SL operation |
vivo |
| R2-2009827 |
38.304 Correction on cell (re)selection for sidelink UE |
vivo |
| R2-2009828 |
36.304 Correction on cell (re)selection for sidelink UE |
vivo |
| R2-2009836 |
Transmission of SidelinkUEInformation |
Google Inc. |
| R2-2009837 |
Transmission of SidelinkUEInformationNR |
Google Inc. |
| R2-2009989 |
Correction to ASN.1 inclusion conditions for V2X SL and UL prioritization thresholds |
MediaTek Inc., Ericsson, vivo, OPPO |
| R2-2009990 |
Clarification with respect to validity of configured SL grant type 1 received in HO command |
Nokia, Nokia Shanghai Bell |
| R2-2010012 |
Correction on configured grant validity under RLF |
Nokia, Nokia Shanghai Bell |
| R2-2010017 |
Discussion of SLRB configuration mismatch |
Nokia, Nokia Shanghai Bell |
| R2-2010060 |
Correction on SL configured grant type 1 validity under RLF |
Nokia, Nokia Shanghai Bell |
| R2-2010235 |
Corrections on 36.331 for LTE V2X cross RAT configuration |
ZTE Corporation, Sanechips |
| R2-2010300 |
Miscellaneous corrections on TS 36.331 |
Huawei, Hisilicon |
| R2-2010301 |
Miscellaneous corrections on TS 38.331 |
Huawei, Hisilicon |
| R2-2010302 |
Correction on trigger of SL specific MAC reset in TS 38.331 |
Huawei, Hisilicon |
| R2-2010421 |
Corrections on resource reservation period configuration |
ASUSTeK |
| R2-2010422 |
Correction on RRC reconfiguration failure for SL |
ASUSTeK |
| R2-2010423 |
Correction on RRC reconfiguration failure for SL |
ASUSTeK |
| R2-2010442 |
On synchronization alignment between V2X SL and NR SL in the in-device coexistence environment |
Huawei, HiSilicon |
| R2-2010443 |
Correction on sidelink capability transfer procedure |
Huawei, HiSilicon |
| R2-2010463 |
Issue on ping pong state transition for sidelink UE |
Xiaomi communications, China Mobile, Apple, Huawei |
| R2-2010464 |
Introduction of Sidelink Data Inactivity monitoring |
Xiaomi communications, China Mobile, Apple, Huawei |
| R2-2010465 |
Introduction of Sidelink Data Inactivity monitoring |
Xiaomi communications, China Mobile, Apple, Huawei |
| R2-2010466 |
Introduction of Sidelink Data Inactivity monitoring |
Xiaomi communications, China Mobile, Apple, Huawei |
| R2-2010495 |
Miscellaneous corrections on TS 38.331 |
Huawei, Hisilicon |
| R2-2010678 |
Correction on MCS range |
OPPO |
| R2-2010931 |
Summary of [AT112-e][705][V2X] Miscellaneous corrections |
Huawei (Rapporteur) |
| R2-2010932 |
Miscellaneous corrections on TS 38.331 |
Huawei, HiSilicon |
| R2-2010933 |
LS on per table MCS range for mode-2 |
RAN2 |
| R2-2010934 |
Summary of [AT112-e][707][V2X] – Discussion on the remaining issue from R2-2009053 |
Huawei, HiSilicon |
| R2-2010935 |
Correction on RRC parameters for NR SL communication |
Huawei, HiSilicon |
| R2-2010936 |
Summary of [AT112-e][708][V2X] SL related RRC procedure |
Ericsson |
| R2-2010937 |
Corrections on sidelink related RRC procedures |
Ericsson |
| R2-2010938 |
Summary of [AT112-e][709][V2X]: Left issue on inter-frequency operation (OPPO) |
OPPO |
| R2-2010939 |
Correction on inter-frequency operation |
OPPO |
| R2-2010940 |
Summary of [AT112-e][710][V2X] Left issue on UE capability |
Ericsson |
| R2-2010959 |
Correction on inter-frequency operation |
OPPO |
| R2-2010962 |
Miscellaneous corrections on TS 36.331 |
Huawei, HiSilicon |
| R2-2010986 |
Summary of AI 6.4.2 — CP corrections for 5G V2X with NR SL |
Huawei, HiSilicon |
| R2-2010997 |
Introduction of Sidelink Data Inactivity monitoring |
Xiaomi communications, China Mobile, Apple, Huawei |
| 6.4.3 |
User plane corrections |
|
| R2-2008781 |
Correction for cast type indicator |
OPPO |
| R2-2008782 |
Correction on CG maximum retransmission number |
OPPO |
| R2-2008783 |
Miscellaneous correction on NR V2X |
OPPO |
| R2-2008798 |
36321_Correction of prioritization between SL and UL |
OPPO |
| R2-2008799 |
38321_Correction of prioritization between SL and UL |
OPPO |
| R2-2008800 |
Discussion on resource and HARQ process id of configured grant |
OPPO |
| R2-2008801 |
Discussion on resource and HARQ process id of configured grant |
OPPO |
| R2-2008879 |
clarification on priority handling |
CATT |
| R2-2009044 |
Discussion on CG resource calculation |
ZTE Corporation, Sanechips |
| R2-2009045 |
CR for TS 38.321 on calculation of CG type1 and type 2 |
ZTE Corporation, Sanechips |
| R2-2009046 |
Correction on resource reselection for (pre-)emption |
ZTE Corporation, Sanechips |
| R2-2009047 |
CR for TS 38.321 for NR V2X on miscellaneous issues |
ZTE Corporation, Sanechips |
| R2-2009050 |
[draft]LS on calculation of CG type 1 and type 2 |
ZTE Corporation, Sanechips |
| R2-2009052 |
CR for TS 36.321 for NR V2X on miscellaneous issues |
ZTE Corporation, Sanechips |
| R2-2009182 |
Priority handling on CSI reporting MAC CE |
Ericsson |
| R2-2009207 |
Correction on Zone Configuration per Communication Range |
InterDigital, Apple |
| R2-2009208 |
Discussion on setting of range parameter in SCI |
InterDigital, Apple, Ericsson, Qualcomm, Nokia, Mediatek, Fraunhofer HHI, Fraunhofer IIS, Convida Wireless |
| R2-2009209 |
Corrections for setting of range parameter in SCI |
InterDigital, Apple, Ericsson, Qualcomm, Nokia, Mediatek, Fraunhofer HHI, Fraunhofer IIS, Convida Wireless |
| R2-2009217 |
Correction to sidelink MAC reset |
Ericsson |
| R2-2009218 |
corrections to MAC spec regarding SL-CSI reporting MAC CE |
Ericsson |
| R2-2009219 |
Correction to SL grant terminology |
Ericsson |
| R2-2009220 |
Correction to SL configured grant activation and deactivation |
Ericsson |
| R2-2009221 |
Corrections on counting number of transmissions of a MAC PDU |
Ericsson |
| R2-2009222 |
corrections to MAC spec regarding CG deactivation - Option 1 |
Ericsson |
| R2-2009223 |
corrections to MAC spec regarding CG deactivation - Option 2 |
Ericsson |
| R2-2009224 |
corrections to RRC spec regarding CG deactivation - Option 2 |
Ericsson |
| R2-2009225 |
corrections to MAC spec regarding prioritization between UL and SL |
Ericsson |
| R2-2009226 |
UE actions in case of CG deactivation |
Ericsson |
| R2-2009227 |
open issues on UL SL prioritization |
Ericsson |
| R2-2009250 |
Report of [Post111-e][707][V2X] CR update to new RAN1 decisions |
LG Electronics France |
| R2-2009252 |
[Post111-e][707][V2X] Corrections to 5G V2X with NR Sidelink |
LG Electronics France |
| R2-2009253 |
Correction to pre-emption check for Sidelink resource allocation mode 2 |
LG Electronics France |
| R2-2009254 |
Corrections to SR prioritization for NR sidelink communication |
LG Electronics France |
| R2-2009318 |
Discussion on resource determination of SL configured grant |
SHARP Corporation |
| R2-2009519 |
Correction on TX UE handling of last transmission of MAC PDU |
Apple, InterDigital Inc. |
| R2-2009829 |
Support RLC Re-establishment |
vivo |
| R2-2009830 |
misalignment SL/UL prioritization betwwen MAC and PHY |
vivo |
| R2-2009831 |
Miscellaneous corrections for MAC |
vivo |
| R2-2010010 |
On toggling of the NDI in SL resource allocation mode 1 |
Nokia, Nokia Shanghai Bell |
| R2-2010080 |
Correction to the logical channel selection procedure |
Nokia, Nokia Shanghai Bell |
| R2-2010186 |
Correction to sidelink specific MAC reset |
Samsung Electronics |
| R2-2010303 |
Miscellaneous corrections on TS 38.321 |
Huawei, Hisilicon |
| R2-2010304 |
Correction on MCS selection |
Huawei, Hisilicon |
| R2-2010305 |
Correction on the clear of dynamic sidelink grants |
Huawei, Hisilicon |
| R2-2010306 |
Correction on the UE behaviour before the next period of SL CG |
Huawei, Hisilicon |
| R2-2010307 |
Correction on the prioritization between UL MAC PDU and SL SR |
Huawei, Hisilicon |
| R2-2010308 |
Correction on the handling of collision among multiple SL grants |
Huawei, Hisilicon |
| R2-2010309 |
Correction on the MAC reset |
Huawei, Hisilicon |
| R2-2010310 |
Correction on HARQ process ID calculation for SL CG |
Huawei, Hisilicon |
| R2-2010311 |
Correction on the condition to clear configured sidelink grant |
Huawei, Hisilicon |
| R2-2010312 |
Correction on resource (re-)selection for mode 2 |
Huawei, Hisilicon |
| R2-2010313 |
Discussion on sidelink process association |
Huawei, Hisilicon |
| R2-2010314 |
Discussion on NDI maintenance |
Huawei, Hisilicon |
| R2-2010315 |
Discussion on Sidelink process management for RX UE |
Huawei, Hisilicon |
| R2-2010316 |
Discussion on retransmission on the selected sidelink grant and the configured sidelink grant |
Huawei, Hisilicon |
| R2-2010424 |
MAC Corrections for NR V2X |
ASUSTeK |
| R2-2010425 |
RRC Corrections for SL PUCCH configuration |
ASUSTeK |
| R2-2010491 |
Correction on resource re-selection |
vivo |
| R2-2010677 |
Correction on MCS range |
OPPO |
| R2-2010948 |
Corrections to 5G V2X with NR Sidelink |
LG Electronics Inc. |
| R2-2010949 |
Miscellaneous Corrections to 5G V2X with NR Sidelink |
LG Electronics Inc. |
| R2-2010950 |
[AT112-e][713][V2X] MAC corrections (LG) |
LG Electronics Inc. (Rapporteur) |
| R2-2010951 |
Correction on the MAC reset |
Huawei, HiSilicon, Ericsson, Samsung Electronics |
| R2-2010952 |
Summary of [AT112-e][714][V2X] MAC reset CR (Huawei) |
Huawei (Rapporteur) |
| R2-2010955 |
Correction on the SL process handling |
Huawei, HiSilicon |
| R2-2010956 |
Summary of [AT112-e][715][V2X] SL process related corrections (Huawei) |
Huawei (Rapporteur) |
| R2-2010957 |
Corrections to UL/SL Prioritization for 5G V2X with NR Sidelink |
LG Electronics Inc. |
| R2-2010963 |
Reply LS on the re-keying procedure for NR SL |
RAN2 |
| R2-2010964 |
[AT112-e][713][V2X] MAC corrections (LG) |
LG Electronics Inc. (Rapporteur) |
| R2-2010965 |
Corrections to UL/SL Prioritization for 5G V2X with NR Sidelink |
LG Electronics Inc. |
| R2-2010977 |
Left issues on security handling |
OPPO, CATT |
| R2-2010978 |
[Draft] Reply LS on the re-keying procedure for NR SL |
CATT |
| R2-2010982 |
Review Report on MAC CRs in AI 6.4.3 |
LG Electronics Inc. (Rapporteur) |
| 6.4.4 |
UE capabilities |
|
| R2-2008785 |
Summary of [POST111-e][708][V2X] Update of capability CRs (OPPO) |
OPPO |
| R2-2008786 |
Draft 38.331 CR for V2X UE capability |
OPPO |
| R2-2008787 |
Draft 38.306 CR for V2X UE capability |
OPPO |
| R2-2008788 |
Draft 36.331 CR for V2X UE capability |
OPPO |
| R2-2008789 |
Draft 36.306 CR for V2X UE capability |
OPPO |
| R2-2008938 |
Correction on LTE V2X UE capability |
OPPO, Huawei, HiSilicon, Samsung |
| R2-2009707 |
Correction on UECapabilityEnquirySidelink (Alt.2) |
Ericsson |
| R2-2009708 |
Correction on UECapabilityEnquirySidelink (Alt.1) |
Ericsson |
| R2-2009716 |
Clarificationon on field description for supportedBandCombinationListSidelinkEUTRA-NR |
Ericsson |
| R2-2009717 |
Correction on setting frequencyBandListFilterSidelink over PC5 |
Ericsson |
| R2-2009719 |
Clarification on field description for supportedBandCombinationListSidelinkEUTRA-NR |
Ericsson |
| R2-2010941 |
Corrections on sidelink UE capabilities |
Ericsson |
| R2-2010943 |
Draft 38.331 CR for V2X UE capability |
OPPO |
| R2-2010944 |
Draft 38.306 CR for V2X UE capability |
OPPO |
| R2-2010945 |
Update on V2X UE capability |
OPPO |
| R2-2010946 |
Update on V2X UE capability |
OPPO |
| R2-2010947 |
Summary of [AT112-e][711][V2X] V2X UE capability (OPPO) |
OPPO |
| R2-2010958 |
Clarification on field description for supportedBandCombinationListSidelinkEUTRA-NR |
Ericsson |
| 6.5.1 |
General and Stage-2 corrections |
|
| R2-2008752 |
Reply LS on 3GPP NR Rel-16 URLLC and IIoT performance evaluation (RP-202097; contact: Ericsson) |
RAN |
| 6.5.2 |
RRC Corrections |
|
| R2-2008864 |
Clarification on referenceTimePreferenceReporting in RRC Reconfiguration Procedure |
CATT |
| R2-2009499 |
Clarification of Uplink Cancellation Priority Configuration |
Apple |
| R2-2009909 |
CR on 38.331 for DL BWP configuration and LCH configuration for NRIIOT |
ZTE Corporation, Sanechips |
| R2-2010101 |
Correction on UE preference for reference time information provisioning |
Huawei, HiSilicon |
| R2-2010102 |
Correction regarding TimeReferenceSFN only for CG Type 1 |
Huawei, HiSilicon |
| R2-2010103 |
Correction regarding reconfigure EHC |
Huawei, HiSilicon |
| R2-2011128 |
Summary of [AT112-e][040][IIOT] RRC and UE cap Corrections |
CATT |
| R2-2011129 |
Clarification on referenceTimePreferenceReporting in RRC Reconfiguration Procedure |
CATT, Ericsson |
| R2-2011209 |
Correction regarding reconfigure EHC |
Huawei, HiSilicon, Ericsson, Samsung |
| R2-2011211 |
CR on 38.331 for DL BWP configuration and LCH configuration for NRIIOT |
ZTE Corporation, Sanechips |
| R2-2011268 |
Correction on field description of configuredGrantConfigType2DeactivationStateList |
ZTE Corporation, Sanechips |
| 6.5.3 |
MAC Corrections |
|
| R2-2009048 |
CR on 38.321 for the UL transmission scheduled with TC-RNTI |
ZTE Corporation, Sanechips |
| R2-2009372 |
Correction on resource overlapping with grants addressed to T-C-RNTI |
Huawei, HiSilicon |
| R2-2009373 |
Clarification on the condition of a de-prioritized grant |
Huawei, HiSilicon |
| R2-2009374 |
Clarification of configuration for physical layer prioritization |
Huawei, HiSilicon |
| R2-2009375 |
Clarification of PHY behaviour for Data & SR overlapping with equal L1 priority |
Huawei, HiSilicon |
| R2-2009483 |
Clarification on the SR and PUSCH conflict with equal LCH priority |
Apple |
| R2-2009500 |
Configuration Options for Intra-UE Prioritization |
Apple |
| R2-2009539 |
Correction on autonomous transmission for the deprioritized CG-Alt1 |
OPPO |
| R2-2009540 |
Correction on autonomous transmission for the deprioritized CG-Alt2 |
OPPO |
| R2-2009541 |
Consideration on L2 priority and PHY priority feature |
OPPO |
| R2-2009599 |
Priority of Uplink Grant |
Samsung, Ericsson |
| R2-2009752 |
Clarification of Grant Priority Determination |
Nokia, Nokia Shanghai Bell |
| R2-2009753 |
Configured grant timer termination upon PUSCH cancellation |
Nokia, Nokia Shanghai Bell |
| R2-2010052 |
Correction for SPS HARQ process ID calculation |
Ericsson |
| R2-2010053 |
Clarification for CG overlapping with PUSCH duration of MSGA |
Ericsson |
| R2-2010054 |
Intra-UE Prioritization inter-group feature dependency |
Ericsson |
| R2-2010100 |
Correction on construction of Multiple Entry CG Confirmation MAC CE |
Huawei, HiSilicon |
| R2-2010522 |
Correction of Multiple Entry Configured Grant Confirmation |
Samsung |
| R2-2010525 |
PUSCH Carrying Multiplexed UCI in Intra-UE Prioritization |
Samsung |
| R2-2011058 |
Summary of [AT112-e][041][IIOT] MAC I |
Huawei, HiSilicon |
| R2-2011074 |
Summary of email discussion [AT112-e][043][IIOT] MAC II (Nokia) |
Nokia |
| R2-2011075 |
Configured Grant related MAC CR for IIoT |
Nokia, Nokia Shanghai Bell, Ericsson, Samsung |
| R2-2011124 |
LS on overlapped data and SR are of equal L1 priority |
RAN2 |
| R2-2011143 |
Correction for SPS HARQ process ID calculation |
Ericsson |
| R2-2011144 |
Correction on resource overlapping with grants addressed to T-C-RNTI |
Huawei, HiSilicon |
| R2-2011153 |
Report of Offline 042: MAC II (Samsung) |
Samsung |
| R2-2011154 |
Correction for Priority of Uplink Grant |
Samsung, Ericsson |
| R2-2011157 |
Correction on resource overlapping with grants addressed to TC-RNTI |
Huawei, HiSilicon |
| R2-2011210 |
Clarification on the condition of a de-prioritized grant |
Huawei, HiSilicon |
| 6.5.4 |
PDCP Corrections |
|
| R2-2011006 |
Summary on [AT112-e][044][IIOT] PDCP Corrections |
Ericsson |
| R2-2011056 |
Corrections for PDCP duplication introduced in IIoT |
Ericsson |
| R2-2011197 |
Corrections for PDCP duplication introduced in IIoT |
Ericsson |
| 6.5.4.1 |
Duplication |
|
| R2-2009908 |
Correction on 38.323 for PDCP duplication with more than two RLC entities for SRB |
ZTE Corporation, Sanechips |
| R2-2010055 |
Corrections for PDCP duplication |
Ericsson |
| 6.5.4.2 |
Ethernet Header Compression |
|
| R2-2009564 |
CR on LTE PDCP re-establishment for UM DRB when t-Reordering is used |
Samsung |
| R2-2010056 |
Corrections for EHC |
Ericsson |
| R2-2011063 |
CR on LTE PDCP re-establishment for UM DRB when t-Reordering is used |
Samsung |
| 6.5.5 |
Other |
|
| R2-2008863 |
Correction on dynamic PUSCH skipping when PUCCH with UCI overlaps with PUSCH |
CATT |
| R2-2009376 |
Correction on the pre-requisite condition for dci-UL-PriorityIndicator-r16 |
Huawei, HiSilicon |
| 6.6.1 |
General and Stage 2 corrections |
|
| R2-2008746 |
Reply LS on positioning SRS during DRX inactive time (R4-2012143; contact: Apple) |
RAN4 |
| R2-2008748 |
LS on new measurement gap patterns for positioning measurements (R4-2012285; contact: Ericsson) |
RAN4 |
| R2-2008803 |
Minor corrections on TS 36.305 |
CATT |
| R2-2008804 |
Minor corrections on TS 38.305 |
CATT |
| R2-2008805 |
Correction on the NOTE in architecture figure in TS 38.305 |
CATT |
| R2-2009000 |
Remove the NOTE in architecture figure in TS 38.305 |
Intel Corporation |
| R2-2010067 |
Activation Time for Periodic UL SRS Transmission |
Ericsson |
| R2-2010068 |
Correction to SUPL support for NR positioning methods |
Ericsson |
| R2-2010069 |
Correction of stage 2 positioning architecture aspects |
Ericsson |
| R2-2010070 |
Missing Updates for Aperiodic UL SRS Support |
Ericsson |
| R2-2010092 |
SUPL support for NR positioning methods |
Qualcomm Incorporated |
| R2-2010141 |
Corrections to E-CID and NR E-CID positioning |
Nokia, Nokia Shanghai Bell |
| R2-2010266 |
Miscellaneous corrections for 38305 |
Huawei, HiSilicon |
| R2-2010267 |
Correction to stage2 spec for SRS (de-)activaton |
Huawei, HiSilicon |
| R2-2010268 |
Correction to stage2 of NR ECID |
Huawei, HiSilicon |
| R2-2010573 |
Clarification on usage of ECID procedure |
Ericsson |
| R2-2010574 |
Updates on missing deferred location requests |
Ericsson |
| R2-2010575 |
Alignment of the position information format with SA2 specification |
Ericsson |
| R2-2010657 |
Miscellaneous correction for stage 2 |
Ericsson |
| R2-2010674 |
Summary document for agenda item 6.6.1 - NR Positioning Stage2 |
Nokia, Nokia Shanghai Bell |
| R2-2010863 |
NR positioning Stage 2 corrections |
Nokia (Rapporteur), Ericsson, Huawei |
| R2-2010876 |
Offline 603 on NR Positioning Stage 2 Corrections |
Nokia (Rapporteur) |
| R2-2010882 |
NR positioning Stage 2 corrections |
Nokia (Rapporteur), Ericsson, Huawei |
| R2-2010992 |
Correction to stage2 spec for SRS (de-)activaton |
Huawei, HiSilicon, Ericsson |
| R2-2011138 |
LS on new per-UE MG for NR positioning (R4-2014282; contact: Apple) |
RAN4 |
| 6.6.2 |
RRC corrections |
|
| R2-2008806 |
Corrections on 38.331 to capture agreements of area scope for posSIB validity |
CATT, Ericsson |
| R2-2008807 |
Corrections on description of sfn-Offset and sfn0-Offset in SSB-Configuration in TS 38.331 |
CATT |
| R2-2008808 |
Correction on the missed description of sfn-SSB-Offset in SSB-Configuration in TS 38.331 |
CATT |
| R2-2010071 |
Corrections and update for RRC Positioning |
Ericsson |
| R2-2010269 |
CR on SI window for positioning SI message |
Huawei, HiSilicon |
| R2-2010270 |
Correction on posSRS configuration |
Huawei, HiSilicon |
| R2-2010272 |
Correction on acquisition of MIB and SIB1 |
Huawei, HiSilicon, Ericsson |
| R2-2010273 |
Correction on posSIB broadcastStatus |
Huawei, HiSilicon |
| R2-2010709 |
Summary for RRC Corrections for Positioning |
Ericsson |
| R2-2010864 |
Positioning RRC updates for posSIB validity check and field description correction |
Ericsson |
| R2-2010875 |
Offline 604 Positioning RRC proposals |
Ericsson (Rapporteur) |
| R2-2010991 |
Corrections of field descrption of sfn-Offset and sfn-SSB-Offset |
Ericsson, CATT, Huawei, HiSilicon |
| R2-2011190 |
Correction on acquisition of MIB and SIB1 |
Huawei, HiSilicon, Ericsson |
| 6.6.3 |
LPP corrections |
|
| R2-2008809 |
Correction on sfn-SSB-Offset in NR-SSB-Config-r16 in TS 37.355 |
CATT |
| R2-2009042 |
Discussion on whether PRS ID can be reused on different frequency layers |
vivo Mobile Communication Co., |
| R2-2010093 |
Clarification of quality and time stamp for RSTD measurements |
Qualcomm Incorporated |
| R2-2010263 |
Correction on PRS configuration |
Huawei, HiSilicon |
| R2-2010264 |
Correction on NR E-CID |
Huawei, HiSilicon |
| R2-2010265 |
LPP corrections on UE capability signaling |
Huawei, HiSilicon |
| R2-2010865 |
Miscelaneous LPP corrections |
Qualcomm Incorporated |
| R2-2010975 |
Summary of LPP corrections agenda item 6.6.3 |
Qualcomm Incorporated |
| R2-2011055 |
Summary of Email discussion [AT112-e][605][POS] LPP proposals |
Qualcomm Incorporated |
| R2-2011073 |
Correction on LPP spec |
Huawei, HiSilicon, Qualcomm Incorporated |
| 6.6.4 |
MAC corrections |
|
| R2-2010066 |
SRS for Positioning transmission in Connected mode DRX |
Ericsson |
| R2-2010271 |
Correction on SP posSRS (de-)activation MAC CE |
Huawei, HiSilicon |
| R2-2010861 |
Correction on SP posSRS (de-)activation MAC CE |
Huawei, HiSilicon, OPPO |
| R2-2011279 |
Correction on SP posSRS (de-)activation MAC CE |
Huawei, HiSilicon, OPPO |
| 6.7.1 |
General and Stage-2 Corrections |
|
| R2-2009312 |
Miscellaneous corrections to Mobility Enhancements |
Nokia (Rapporteur), Ericsson, Intel Corporation, Nokia Shanghai Bell, Sanechips, ZTE |
| R2-2009386 |
Clarification on CHO in LTE-DC |
ZTE Corporation, Sanechips |
| R2-2009995 |
Clarification of CHO simultaneous with DAPS |
Ericsson |
| R2-2010187 |
Correction on TS 38.300 for CHO |
Huawei, HiSilicon |
| R2-2010188 |
Correction on TS 36.300 for CHO |
Huawei, HiSilicon |
| R2-2010354 |
Miscellaneous corrections for Mobility Enhancements |
ZTE Corporation, Sanechips, Ericsson |
| R2-2010651 |
Correction to RLF in case of DAPS HO |
Samsung Electronics Co., Ltd |
| R2-2010715 |
Report from [AT112-e][210][MOB] Stage-2 corrections (Nokia) |
Nokia, Nokia Shanghai Bell |
| R2-2010716 |
MobEnh Stage-2 corrections |
Nokia (rapporteur), Nokia Shanghai Bell, NEC, Intel Corporation, ZTE, Sanechips, Ericsson |
| R2-2010717 |
Miscellaneous corrections to Mobility Enhancements |
Nokia (Rapporteur), Ericsson, Intel Corporation, Nokia Shanghai Bell, Sanechips, ZTE Corporation |
| R2-2010718 |
Miscellaneous corrections for Mobility Enhancements |
ZTE Corporation (Rapporteur), Sanechips, Ericsson, Nokia, Nokia Shanghai Bell |
| R2-2011101 |
Correction to RLF in case of DAPS HO |
Samsung |
| R2-2011208 |
LS on support of NUL and SUL during DAPS handover (R1-2009682; contact: Intel) |
RAN1 |
| 6.7.2 |
Conditional handover related corrections |
|
| R2-2009472 |
Target cell ID parsing in CHO and CPAC |
Apple |
| R2-2009533 |
Correction on configuration of triggerCondition for CHO |
CATT |
| R2-2009639 |
Correction to conditional reconfiguration evaluation |
ITRI |
| R2-2009640 |
Correction to remove conditional reconfiguration related measurement configuration |
ITRI |
| R2-2009848 |
Correction to attemptCondReconfig in ConditionalReconfiguration |
Ericsson |
| R2-2009996 |
Missing release of VarConditionalReconfig |
Ericsson |
| R2-2009997 |
Missing release of VarConditionalReconfiguration |
Ericsson |
| R2-2009998 |
Inability to comply with conditional reconfiguration |
Ericsson |
| R2-2010189 |
Correction on TS 38.331 for CHO |
Huawei, HiSilicon |
| R2-2010190 |
Correction on TS 36.331 for CHO |
Huawei, HiSilicon |
| R2-2010205 |
Issue on failure handling of handover without key change for the UE configured with attemptCondReconfig |
SHARP Corporation |
| R2-2010206 |
Correction of reconfiguration with sync failure procedure for the UE configured with attemptCondReconfig |
SHARP Corporation |
| R2-2010229 |
Support of Rel-16 features for SCG in EN-DC and NR-DC |
Huawei, HiSilicon |
| R2-2010251 |
UE information transmission in LTE CHO case |
SHARP Corporation, Ericsson |
| R2-2010252 |
Clarification on UE information transmission in CHO case(36.331) |
SHARP Corporation, Ericsson |
| R2-2010253 |
UE information transmission in NR CHO case |
SHARP Corporation, Ericsson |
| R2-2010254 |
Clarification on UE information transmission in CHO case(38.331) |
SHARP Corporation, Ericsson |
| R2-2010719 |
Summary of discussion [211][MOB] CHO/CPC RRC corrections (Intel) |
Intel Corporation |
| R2-2010720 |
Miscellaneous corrections for conditional reconfiguration |
Intel Corporation (Rapporteur) |
| R2-2010721 |
Miscellaneous corrections for conditional reconfiguration |
Intel Corporation (Rapporteur) |
| R2-2010756 |
Missing release of VarConditionalReconfiguration |
Ericsson |
| R2-2010757 |
Correction to attemptCondReconfig in ConditionalReconfiguration |
Ericsson |
| R2-2011051 |
Support of Rel-16 features for SCG in EN-DC and NR-DC |
Huawei, HiSilicon |
| R2-2011095 |
Report from [AT112-e][216][MOB] Check CHO-related parts of R2-2010229 (RAN2 VC) |
Nokia, Nokia Shanghai Bell |
| 6.7.3 |
Conditional PSCell change for intra-SN corrections |
|
| R2-2009766 |
Corrections to CPC with and without SRB3 involved |
Nokia, Nokia Shanghai Bell, ZTE Corporation (Rapporteur) |
| R2-2010589 |
Correction to CG-Config for CPC |
Google Inc. |
| R2-2011100 |
Corrections to CPC with and without SRB3 involved |
Nokia, Nokia Shanghai Bell, ZTE Corporation (Rapporteur) |
| 6.7.4 |
UE capability corrections |
|
| R2-2008827 |
NR DAPS capability corrections |
Nokia, Nokia Shanghai Bell |
| R2-2008828 |
NR DAPS capability corrections |
Nokia, Nokia Shanghai Bell |
| R2-2008829 |
NR DAPS capability corrections |
Nokia, Nokia Shanghai Bell |
| R2-2009273 |
The supported combination among FRx/xDD CHO/CPC capabilities |
Intel Corporation |
| R2-2009281 |
Clarification on the setting of FRx&xDD CHO&CPC capabilities |
Intel Corporation |
| R2-2009655 |
Correction on CA-ParametersNR for DAPS handover |
NEC |
| R2-2009783 |
UE Capabilities for Intra-frequency DAPS Handover |
MediaTek Inc. |
| R2-2010292 |
Report of [Post111-e][921][DAPS] DAPS capability structure clarifications (Huawei) |
Huawei, HiSilicon |
| R2-2010293 |
Clarification on NR DAPS UE capability |
Huawei, HiSilicon |
| R2-2010296 |
Clarification on CHO and CPC capabilities between different modes |
Huawei, HiSilicon |
| R2-2010500 |
Remaining open issues for DAPS capabilities |
Ericsson |
| R2-2010722 |
Report of [AT112-e][212][MOB] Mobility UE capabilities for LTE and NR (Huawei) |
Huawei |
| R2-2010723 |
UE capability corrections to Mobility Enhancements (LTE) |
Nokia, Nokia Shanghai Bell, Huawei, HiSilicon |
| R2-2010724 |
UE capability corrections to Mobility Enhancements (LTE) |
Nokia, Nokia Shanghai Bell |
| R2-2010725 |
Miscellaneous corrections to Mobility Enhancements (NR) |
Huawei, HiSilicon |
| R2-2010726 |
Miscellaneous corrections to Mobility Enhancements (NR) |
Huawei, HiSilicon |
| R2-2010751 |
Clarification to NR DAPS UE capability |
Nokia, Nokia Shanghai Bell |
| R2-2010752 |
Clarification to NR DAPS UE capability |
Nokia, Nokia Shanghai Bell |
| R2-2011103 |
Report of [AT112-e][215][NR][MOB] Additional clarification to DAPS capabilities (Nokia) |
Nokia, Nokia Shanghai Bell |
| R2-2011240 |
Clarification on NR DAPS UE capability |
Huawei, HiSilicon |
| 6.7.5 |
Other |
|
| R2-2009665 |
Minor corrections to NR mobility enhancements |
Lenovo, Motorola Mobility |
| R2-2010415 |
Correction on DAPS power configuration |
Google Inc. |
| 6.8.1 |
General and Stage-2 Corrections |
|
| R2-2008706 |
Reply LS on UL PC for NR-DC (R1-2007261; contact: Apple) |
RAN1 |
| R2-2008736 |
Reply LS on power control for NR-DC (R4-2011721; contact: vivo) |
RAN4 |
| R2-2008744 |
LS response on measurement capability for EMR (R4-2012112; contact: Ericsson) |
RAN4 |
| R2-2008750 |
LS on EMR measurement requirements in NR (R4-2012297; contact: Ericsson) |
RAN4 |
| R2-2009548 |
CR for 37.340 on power control for NR_DC |
Nokia, Nokia Shanghai Bell, Samsung, Ericsson |
| R2-2010018 |
Misc corrections for Rel-16 DCCA |
Ericsson |
| R2-2010019 |
Misc corrections for Rel-16 DCCA |
Ericsson |
| R2-2010020 |
Misc corrections for Rel-16 DCCA |
Ericsson |
| R2-2010021 |
Misc corrections for Rel-16 DCCA |
Ericsson |
| R2-2010647 |
Miscellaneous corrections for RRC Transfer procedure |
Samsung R&D Institute UK |
| R2-2010742 |
CR for 37.340 on power control for NR_DC |
Nokia, Nokia Shanghai Bell, Samsung, Ericsson |
| R2-2011118 |
LS reply on cell-grouping UE capability for synchronous NR-DC (R1-2009570; contact: Qualcomm) |
RAN1 |
| R2-2011182 |
Misc corrections for Rel-16 DCCA |
Ericsson |
| R2-2011183 |
Misc corrections for Rel-16 DCCA |
Ericsson |
| R2-2011245 |
Misc corrections for Rel-16 DCCA |
Ericsson |
| 6.8.2 |
Fast Scell activation |
|
| R2-2008927 |
Correction on RA upon BWP switching to dormant BWP |
Asia Pacific Telecom co. Ltd |
| R2-2009549 |
Dormancy correction |
Nokia, Nokia Shanghai Bell |
| R2-2009550 |
BWP support for dormancy |
Nokia, Nokia Shanghai Bell |
| R2-2009573 |
Corrections on bwp-InactivityTimer |
Samsung |
| R2-2010022 |
Timing of direct SCell activation upon RRC configuration |
Ericsson |
| R2-2010731 |
Summary of [AT111-e][221][DCCA] Fast Scell activation and early measurements (Nokia) |
Rapporteur (Nokia) |
| R2-2011087 |
Timing of direct SCell activation upon RRC configuration |
Ericsson |
| 6.8.3 |
Early measurement reporting |
|
| R2-2009352 |
Miscellaneous corrections on early measurement reporting in 38.331 |
CATT |
| R2-2009353 |
Miscellaneous corrections on early measurement reporting in 36.331 |
CATT |
| R2-2009551 |
Measurement applicability and validity |
Nokia, Nokia Shanghai Bell |
| R2-2009552 |
Measurement applicability and validity |
Nokia, Nokia Shanghai Bell |
| R2-2009553 |
Measurement applicability and validity |
Nokia, Nokia Shanghai Bell |
| R2-2010023 |
Serving cell results for early measurements |
Ericsson |
| R2-2010024 |
Early measurement requirements |
Ericsson |
| R2-2010653 |
Reporting of dle/inactive measurement not obtained in the current cell |
Huawei, HiSilicon |
| R2-2010654 |
Reporting of dle/inactive measurement not obtained in the current cell |
Huawei, HiSilicon |
| R2-2010730 |
Summary of [AT112-e][220][DCCA] Simple DCCA corrections |
Ericsson (rapporteur) |
| 6.8.4 |
Other DCCA corrections |
|
| R2-2008968 |
Clarification of NR-DC with unaligned CA |
Qualcomm Incorporated |
| R2-2009354 |
Miscellaneous corrections for Rel-16 DCCA in 38.331 |
CATT |
| R2-2009414 |
Correction on tdm-PatternConfig2 configuration upon MR-DC Release |
MediaTek Inc. |
| R2-2009415 |
Correction on tdm-PatternConfig2 configuration upon MR-DC Release |
MediaTek Inc. |
| R2-2010025 |
Missing fields for Toffset coordination |
Ericsson, Nokia, Nokia Shanghai Bell |
| R2-2010026 |
Correction on sk-counter in RRCResume |
Ericsson |
| R2-2010027 |
Correction on p-UE-FR2 for NR-DC power control |
Ericsson, NTTDOCOMO |
| R2-2010028 |
Processing delay requirements for DLInformationTransferMRDC |
Ericsson |
| R2-2010112 |
Correction on p-UE-FR2 for NR-DC power control |
Ericsson, NTTDOCOMO |
| R2-2010115 |
Remaining issues on Toffset for NR-DC power control |
Huawei, HiSilicon |
| R2-2010116 |
Correction on SCG-related fields in RRCConnection Resume |
Huawei, HiSilicon |
| R2-2010117 |
Correction for fast MCG link recovery via SRB3 in NR-DC |
Huawei, HiSilicon |
| R2-2010118 |
Processing delay requirements for RRC resume |
Huawei, HiSilicon |
| R2-2010119 |
Processing delay requirements for RRC resume |
Huawei, HiSilicon |
| R2-2010120 |
Miscellaneous corrections for DCCA |
Huawei, HiSilicon |
| R2-2010121 |
Corrections for resume with SCG |
Huawei, HiSilicon |
| R2-2010122 |
Correction for fast MCG link recovery in (NG)EN-DC |
Huawei, HiSilicon |
| R2-2010255 |
UE information transmission in LTE fast MCG recovery case |
SHARP Corporation |
| R2-2010256 |
Clarification on UE information transmission in fast MCG recovery case(36.331) |
SHARP Corporation |
| R2-2010291 |
Correction on p-UE-FR2 in NR-DC power control |
vivo |
| R2-2010340 |
Correction on p-UE-FR2 for NR-DC power control in FR2 |
Huawei, HiSilicon |
| R2-2010378 |
Summary of [Post111-e][918][R16 DCCA] SCell SMTC window for Unaligned CA (CMCC) |
CMCC |
| R2-2010379 |
CR for Unaligned CA in TS 38.331 |
CMCC,MediaTek Inc. |
| R2-2010380 |
CR for Unaligned CA in TS 38.306 |
CMCC,MediaTek Inc. |
| R2-2010566 |
Clarification on ULInformationTransferMRDC |
Google Inc. |
| R2-2010650 |
Corrections on messages encapsulated in ULInformationTransferMRDC |
Samsung R&D Institute UK |
| R2-2010732 |
Summary of [AT112-e][222][DCCA] Miscellaneous DCCA corrections and capabilities (Ericsson) |
Ericsson |
| R2-2010740 |
CR for Unaligned CA in TS 38.331 |
CMCC,MediaTek Inc. |
| R2-2010741 |
CR for Unaligned CA in TS 38.306 |
CMCC,MediaTek Inc. |
| R2-2010743 |
Correction on p-UE-FR2 in NR-DC power control |
vivo |
| R2-2011096 |
Correction for fast MCG link recovery in (NG)EN-DC |
Huawei, HiSilicon |
| R2-2011097 |
Processing delay requirements for DLInformationTransferMRDC |
Ericsson |
| R2-2011194 |
[AT112-e][225][NR][DCCA] Correction on FR2 maximum power for NR-DC power control (vivo) |
vivo |
| R2-2011195 |
Reply LS on power control for NR-DC |
vivo |
| R2-2011196 |
Correction on p-UE-FR2 for NR-DC power control in FR2 |
Huawei, HiSilicon |
| R2-2011242 |
CR for Unaligned CA in TS 38.331 |
CMCC,MediaTek Inc. |
| R2-2011243 |
CR for Unaligned CA signalling in TS 38.331 |
CMCC, MediaTek Inc |
| R2-2011244 |
Correction on SCG-related fields in RRCConnection Resume |
Huawei, HiSilicon |
| R2-2011246 |
Reply LS on power control for NR-DC |
RAN2 |
| 6.8.5 |
UE capabilities |
|
| R2-2009186 |
Correction to 36.306 on UE capability of direct SCell activation |
Qualcomm Incorporated, Ericsson |
| R2-2009187 |
Correction to 36.331 on UE capability of direct SCell activation |
Qualcomm Incorporated, Ericsson |
| R2-2009437 |
Capability for beam level NR early measurement reporting |
MediaTek Inc. |
| R2-2009438 |
Capability for beam level NR early measurement reporting |
MediaTek Inc. |
| R2-2009554 |
Direct Scell activation capability |
Nokia, Nokia Shanghai Bell |
| R2-2009666 |
Adding missing field descriptions of Multi-RAT DC and CA enhancements capabilities |
Lenovo, Motorola Mobility |
| R2-2010029 |
Cell group filtering for NR-DC |
Ericsson |
| R2-2010030 |
Clarification on cross-carrier A-CSI triggering capability |
Ericsson |
| R2-2010031 |
Correction on early measurement capabilities |
Ericsson |
| R2-2010032 |
Correction on early measurement capabilities |
Ericsson |
| R2-2010114 |
UE capability of direct E-UTRAN SCG SCell activation |
Huawei, HiSilicon |
| R2-2010341 |
Adding UE capability for beam level early measurement reporting (36331) |
Huawei, HiSilicon |
| R2-2010342 |
Adding UE capability for beam level early measurement reporting (36306) |
Huawei, HiSilicon |
| R2-2010343 |
Clarification on UE capability of cross-carrier scheduling with different numerologies |
Huawei, HiSilicon |
| R2-2010593 |
MCG and SCG differentiation in asynchronous NR-DC |
Samsung Electronics |
| R2-2010744 |
Capability for beam level NR early measurement reporting |
MediaTek Inc., Huawei, HiSilicon |
| R2-2010745 |
Capability for beam level NR early measurement reporting |
MediaTek Inc., Huawei, HiSilicon |
| R2-2010746 |
Summary of [AT112-e][227][NR][DCCA] Remaining capability topics for DCCA (Ericsson) |
Ericsson |
| R2-2010844 |
Correction to 36.331 on UE capability of direct SCell activation |
Qualcomm Incorporated, Ericsson |
| R2-2011088 |
Correction on early measurement capabilities and descriptions |
Ericsson, Lenovo, Motorola Mobility |
| R2-2011098 |
Clarification on cross-carrier A-CSI triggering capability |
Ericsson |
| R2-2011110 |
Dummify UE capability of crossCarrierScheduling-OtherSCS |
Huawei, HiSilicon |
| R2-2011111 |
Dummify UE capability of crossCarrierScheduling-OtherSCS |
Huawei, HiSilicon |
| R2-2011112 |
Dummify UE capability of crossCarrierScheduling-OtherSCS |
Huawei, HiSilicon |
| R2-2011113 |
Dummify UE capability of crossCarrierScheduling-OtherSCS |
Huawei, HiSilicon |
| 6.9.1 |
General and Stage-2 corrections |
|
| R2-2008726 |
Reply LS on NR SCG release for power saving (R3-205764; contact: ZTE) |
RAN3 |
| R2-2008745 |
Reply LS on RRM relaxation in power saving (R4-2012122; contact: Huawei) |
RAN4 |
| 6.9.2 |
User plane Corrections |
|
| R2-2008953 |
MAC CR for specification redundance between MAC and PHY |
Xiaomi Communications |
| R2-2009691 |
Correction on DCP for power sving |
vivo |
| R2-2010832 |
MAC CR for specification redundance between MAC and PHY |
Xiaomi Communications |
| R2-2010904 |
MAC CR for specification redundance between MAC and PHY |
Xiaomi Communications |
| 6.9.3 |
Control plane Corrections |
|
| R2-2009079 |
Duplicated capture for RRM relaxation in RAN2 and RAN4 |
vivo |
| R2-2009080 |
Summary of RRM relaxation behaviors |
vivo, CATT |
| R2-2009081 |
[Draft] LS to RAN4 on RRM measurement relaxation in power saving |
vivo |
| R2-2009082 |
Correction on field description of highPriorityMeasRelax |
vivo |
| R2-2009370 |
Correction on cell reselection within 1 hour measurement interval |
CATT |
| R2-2009462 |
UE assistance information for DRX preference on secondary DRX group - Option1 |
OPPO, Ericsson |
| R2-2009463 |
UE assistance information for DRX preference on secondary DRX group - Option2 |
OPPO, Ericsson, Qualcomm, Apple, Xiaomi |
| R2-2009928 |
Correction on RRC state preference - Opt 1 |
Nokia, Nokia Shanghai Bell |
| R2-2009929 |
Correction on RRC state preference – Opt 2 |
Nokia, Nokia Shanghai Bell |
| R2-2009952 |
Way forward relaxed RRM requirements in RAN2 and RAN4 |
Ericsson |
| R2-2010243 |
Correction on otherConfig for RRCResume |
Huawei, HiSilicon |
| R2-2010595 |
Correction on RRM relaxation |
Samsung Electronics |
| R2-2010597 |
Correction on cell reselection within 1 hour measurement interval |
CATT |
| R2-2010821 |
Correction on RRC state preference |
Nokia, Nokia Shanghai Bell |
| R2-2010833 |
Correction on RRM relaxation |
Samsung Electronics, CATT |
| R2-2010842 |
UE assistance information for DRX preference |
OPPO, Ericsson |
| 6.10.1 |
General and stage-2 corrections |
|
| R2-2008764 |
LS Reply on QoS Monitoring for URLLC (S5-204537; contact: Intel) |
SA5 |
| R2-2008765 |
Reply LS on the user consent for trace reporting (S5-204542; contact: Huawei) |
SA5 |
| R2-2009419 |
User consent principles |
Nokia, Nokia Shanghai Bell, Ericsson |
| R2-2009420 |
Draft reply LS on the user consent for trace reporting |
Nokia, Nokia Shanghai Bell |
| R2-2009679 |
Corrections to TS 37.320 |
vivo |
| R2-2010039 |
Editorial Corrections |
Ericsson, Nokia , CMCC |
| R2-2010040 |
On end of measurement collection period related to WLAN and BT measurements |
Ericsson |
| R2-2010398 |
Summary for AI 6.10.1 on General and stage-2 corrections |
CMCC |
| R2-2010408 |
Clarification on Area Checking |
Samsung |
| R2-2010611 |
On time stamp inclusion for event triggered logged MDT |
Ericsson |
| R2-2010614 |
On Time To Trigger (TTT) configuration associated to L1 event in logged MDT |
Ericsson |
| R2-2010690 |
LS on Clarification on URLLC QoS Monitoring (S2-2007825; contact: Huawei) |
SA2 |
| R2-2010894 |
Reply LS on the user consent for trace reporting |
RAN2 |
| R2-2010895 |
Merged Corrections for TS37.320 |
CMCC, Nokia |
| R2-2010912 |
Merged Corrections for TS37.320 |
CMCC, Nokia |
| 6.10.2 |
TS 38.314 corrections |
|
| R2-2008919 |
Corrections for L2 Measurement |
CATT |
| R2-2009681 |
Miscellaneous corrections to TS 38.314 |
vivo |
| R2-2010038 |
On clarification related to delay measurements in split RAN architecture |
Ericsson |
| R2-2010041 |
Miscellaneous corrections |
Ericsson, CMCC |
| R2-2010042 |
On the usage of #ActiveUEs in inter node messages |
Ericsson |
| R2-2010191 |
Discussion on average Uu delay measurement for L2M |
Huawei, HiSilicon |
| R2-2010192 |
Discussion on D1 measurement for L2M |
Huawei, HiSilicon |
| R2-2010193 |
Correction on TS 38.314 on latency measurements |
Huawei, HiSilicon |
| R2-2010363 |
Summary for AI 6.10.2 on TS 38.314 corrections |
CMCC |
| R2-2010610 |
On EUTRA related L2 measurements for EN-DC |
Ericsson |
| R2-2010612 |
On the clarification of end time of UL PDCP Packet Average Delay |
Ericsson |
| R2-2010656 |
Introduction of MIMO layer based PRB usage measurement |
CMCC |
| R2-2010663 |
Introduction of MIMO layer based PRB usage measurement |
CMCC |
| R2-2011185 |
Introduction of MIMO layer based PRB usage measurement |
CMCC |
| R2-2011186 |
Capture agreements and miscellaneous corrections for layer 2 measurement |
CMCC |
| R2-2011267 |
Introduction of MIMO layer based PRB usage measurement |
CMCC |
| 6.10.3 |
RRC corrections |
|
| R2-2008839 |
Clarification for CEF Report |
CATT |
| R2-2008840 |
Corrections for CEF Report |
CATT |
| R2-2008841 |
Correction on RLF Report for Re-connection |
CATT |
| R2-2008928 |
Correction on RLF Report Content Handover from NR to LTE Failure |
MediaTek Inc. |
| R2-2009421 |
Clarification on UE logging procedure for event-based triger |
Nokia, Nokia Shanghai Bell |
| R2-2009521 |
Correction on RLF Report |
Apple |
| R2-2009522 |
Correction on RLF Report |
Apple |
| R2-2009677 |
Correction to TS 36.331 on logged MDT configuration |
vivo |
| R2-2009678 |
Correction to TS 38.331 on logged MDT configuration |
vivo |
| R2-2009680 |
Miscellaneous corrections to TS 38.331 on SON and MDT |
vivo |
| R2-2009882 |
Correction to MDT |
Google Inc. |
| R2-2010036 |
On miscellaneous corrections |
Ericsson |
| R2-2010037 |
On overriding prevention of signalling based MDT with management based MDT |
Ericsson |
| R2-2010043 |
On ra-purpose field description |
Ericsson |
| R2-2010044 |
Configuration of WLAN BT and Sensor for CEF reporting |
Ericsson |
| R2-2010082 |
Logged MDT support for non-SIB4 frequencies (early measurments) |
Samsung Telecommunications |
| R2-2010083 |
Clarification on logged MDT for non-SIB4 frequencies |
Samsung Telecommunications |
| R2-2010089 |
Ambiguity on retrieval of WLAN and BT location info for Logged MDT |
Samsung Telecommunications |
| R2-2010194 |
Discussion on user consent |
Huawei, HiSilicon |
| R2-2010195 |
Correction on user consent for TS 38.331 |
Huawei, HiSilicon |
| R2-2010196 |
Correction on user consent for TS 36.331 |
Huawei, HiSilicon |
| R2-2010197 |
Correction on user consent for TS 37.320 |
Huawei, HiSilicon |
| R2-2010198 |
Draft reply LS on user consent |
Huawei |
| R2-2010199 |
Correction on the release of obtainCommonLocation |
Huawei, HiSilicon |
| R2-2010200 |
Correction on Inter-RAT SON for 38.331 |
Huawei, HiSilicon |
| R2-2010201 |
Correction on Inter-RAT SON for 36.331 |
Huawei, HiSilicon |
| R2-2010221 |
Summary on 6.10.3 RRC corrections |
Huawei |
| R2-2010327 |
Correction on timer T316 handling |
Samsung Electronics Co., Ltd |
| R2-2010410 |
Miscellaneous Correction on MDT |
Samsung |
| R2-2010581 |
Correction for clearing VarRLF-Report regarding T316 |
Quectel |
| R2-2010582 |
Correction for clearing VarRLF-Report regarding T316 |
Quectel |
| R2-2010590 |
Correction on RA report |
Samsung Electronics |
| R2-2010591 |
Correction on RLF report |
Samsung Electronics |
| R2-2010603 |
Clarification on location configuration in logged MDT |
ZTE Corporation, Sanechips |
| R2-2010604 |
draftCR on location related configuration for logged MDT Alt1 |
ZTE Corporation, Sanechips |
| R2-2010605 |
draftCR on location related configuration for logged MDT Alt2 |
ZTE Corporation, Sanechips |
| R2-2010606 |
Correction to 38331 on RA report |
ZTE Corporation, Sanechips |
| R2-2010607 |
Correction to 38331 on delay measurement |
ZTE Corporation, Sanechips |
| R2-2010609 |
Changes related to RAReport and logged MDT report contents NBC change |
Ericsson |
| R2-2010613 |
On mobility history information associated to Connected mode changes |
Ericsson |
| R2-2010615 |
An indication of reconfiguration with sync type in RLF report |
Ericsson |
| R2-2010616 |
On the lack measResultServingCell availability in Any Cell Selection state |
Ericsson |
| R2-2010617 |
On Neighbour cells measurements in logged MDT |
Ericsson |
| R2-2010618 |
Resolving issues related to PLMN identity list in RAReport |
Ericsson |
| R2-2010619 |
Changes related to RAReport and logged MDT report contents BC change |
Ericsson |
| R2-2010662 |
Correction on RLF Report for Re-connection |
CATT |
| R2-2010890 |
On mobility history information associated to Connected mode changes |
Ericsson |
| R2-2010891 |
Changes related to RAReport and logged MDT report contents BC change |
Ericsson |
| R2-2011010 |
Summary on 6.10.3 RRC corrections |
Huawei |
| R2-2011223 |
Clarification on Logged MDT regarding reporting of WLAN and BT information |
Samsung |
| R2-2011263 |
Report of [AT112-e][888][NR/R16 SON/MDT] Merged SON/MDT 38.331 CR(Huawei) |
Huawei |
| R2-2011264 |
RRC corrections on NR SON and MDT |
Huawei, HiSilicon, Ericsson, Samsung |
| R2-2011265 |
RRC corrections on NR and LTE SON and MDT |
Huawei, HiSilicon, Samsung |
| 6.11.2 |
User plane corrections |
|
| R2-2009794 |
Clarification on the PRACH occasion frequency domain index |
Nokia, Nokia Shanghai Bell |
| R2-2009969 |
2-step RA parameter corrections |
Ericsson |
| R2-2010402 |
Correction on BSR for two-step RA |
Huawei, HiSilicon |
| R2-2010405 |
Correction on DELTA_PREAMBLE for 2-step RA |
Huawei, HiSilicon |
| R2-2011005 |
Correction on DELTA_PREAMBLE and parameters for 2-step RA |
Huawei, HiSilicon, Ericsson, ZTE, Xiaomi, vivo |
| 6.11.3 |
Control plane corrections |
|
| R2-2009968 |
2-step RA parameter corrections |
Ericsson |
| R2-2010403 |
Correction on msgA-PUSCH-Config |
Huawei, HiSilicon |
| R2-2010404 |
Correction on msgA-DMRS-Config |
Huawei, HiSilicon |
| R2-2011062 |
Corrections to 2-Step RA |
Ericsson, Huawei |
| 6.12 |
NR Other Control Plane WIs |
|
| R2-2008753 |
Reply LS on human-readable network name (HRNN) (CP-201361/S1-203197) (S1-203272; contact: vivo) |
SA1 |
| R2-2008762 |
Reply LS on Clarification of CAG only UE accessing EPS network (S2-2007809; contact: Oppo) |
SA2 |
| R2-2009065 |
Considerations on parameter selection for shared cells |
Nokia, Nokia Shanghai Bell |
| R2-2009066 |
Corrections for PNI-NPN related parameter selection |
Nokia, Nokia Shanghai Bell |
| R2-2009625 |
Further Clarification on the Forbidden Tracking Areas |
ZTE Corporation, Sanechips |
| R2-2009626 |
Further Clarification on the NPN-only cell |
ZTE Corporation, Sanechips |
| R2-2009627 |
CR on non-CAG-capable UE |
ZTE Corporation, Sanechips |
| R2-2009628 |
CR on Forbidden Tracking Areas |
ZTE Corporation, Sanechips |
| R2-2009629 |
CR on NPN-only Cell |
ZTE Corporation, Sanechips |
| R2-2010015 |
Selecting index for PLMN, SNPN and UAC parameters |
Ericsson |
| R2-2010016 |
Aligning use of PNI-NPN in RAN2 specs to SA2 specs |
Ericsson |
| R2-2010033 |
Clarification on the total number of CAG identifiers |
Lenovo, Motorola Mobility |
| R2-2010259 |
Dynamic UMTS Radio Capability impact on SRVCC and RACS |
Huawei, HiSilicon, Vodafone, China Unicom |
| R2-2010355 |
Discussion on selected CAG |
Huawei, HiSilicon |
| R2-2010356 |
Discussion on the selection between PLMN and PNI-NPNs |
Huawei, HiSilicon |
| R2-2010407 |
Clarification on SRVCC handover |
Google Inc. |
| R2-2010496 |
Clarification on the selection of suitable cell |
Huawei, HiSilicon |
| R2-2010630 |
38.300 Correction on the SNPN-only cell |
vivo |
| R2-2010631 |
38.300 Correction on CAG information |
vivo |
| R2-2010632 |
38.331 Clarification on the release of RRC connection |
vivo |
| R2-2010761 |
Summary of offline 102 - PRN Stage 3 Corrections |
Nokia |
| R2-2010788 |
Miscellaneous Corrections |
Qualcomm (Rapporteur) |
| R2-2010789 |
Selecting index for PLMN, SNPN and UAC parameters |
Ericsson |
| R2-2010790 |
Dynamic UMTS Radio Capability impact on SRVCC and RACS |
Huawei, HiSilicon, Vodafone, China Unicom |
| R2-2010791 |
Clarification on SRVCC handover |
Google Inc. |
| R2-2010792 |
Clarifying the use of PNI-NPN term in RAN specifications |
Nokia, Ericsson |
| R2-2011162 |
Selecting index for PLMN, SNPN and UAC parameters |
Ericsson, Nokia |
| R2-2011163 |
Dynamic UMTS Radio Capability impact on SRVCC and RACS |
Huawei, HiSilicon, Vodafone, China Unicom |
| R2-2011164 |
LS on UTRAN UE capabilities from CN to gNB |
RAN2 |
| R2-2011231 |
Dynamic UMTS Radio Capability impact on SRVCC and RACS |
Huawei, HiSilicon, Vodafone, China Unicom |
| 6.13 |
NR eMIMO |
|
| R2-2009170 |
Stage-2 description of multi-TRP |
Nokia (Rapporteur) |
| R2-2009905 |
BFR on SCell |
ZTE Corporation, Sanechips, Nokia (Rapporteur) |
| R2-2010769 |
BFR on SCell |
ZTE Corporation, Sanechips, Nokia (Rapporteur) |
| R2-2010770 |
Stage-2 description of multi-TRP |
Nokia (Rapporteur) |
| R2-2010797 |
Summary of [AT112e][107][eMIMO] Stage 2 CRs (Nokia) |
Nokia (Rapporteur) |
| R2-2010798 |
Draft LS on multi-TRP description in Stage-2 |
Nokia |
| R2-2010803 |
Stage-2 description of multi-TRP |
Nokia (Rapporteur) |
| R2-2010804 |
LS on multi-TRP description in Stage-2 |
RAN2 |
| R2-2010901 |
Description of Multi-TRP operation |
Nokia (Rapporteur) |
| 6.13.1 |
User plane corrections |
|
| R2-2009098 |
Correction to parameter list for beam failure recovery procedure |
Samsung Electronics Co., Ltd |
| R2-2009795 |
BFR triggering with candidate beam search |
Nokia, Nokia Shanghai Bell, Ericsson, ZTE |
| R2-2009796 |
Clarification on the BFR trigger upon candidate search |
Nokia, Nokia Shanghai Bell, Ericsson, ZTE |
| R2-2009797 |
Draft LS on BFR requirements time reference |
Nokia |
| R2-2009903 |
38.321 Correction on Enhanced PUCCH Spatial Relation ActivationDeactivation MAC CE |
ZTE Corporation, Sanechips |
| R2-2009904 |
Miscellaneous on 38.321 for BFR and BFR MAC CE |
ZTE Corporation, Sanechips |
| R2-2010009 |
Correction on BFR MAC CE generation |
Qualcomm Incorporated, Samsung |
| R2-2010013 |
Discussion on Enhanced TCI States Activation/Deactivation for UE-specific PDSCH MAC CE on multiple CC case |
Qualcomm Incorporated |
| R2-2010014 |
Correction on Enhanced TCI States Activation/Deactivation for UE-specific PDSCH MAC CE |
Qualcomm Incorporated |
| R2-2010494 |
Correction to bitmap length determination in MAC CEs for BFR |
Fujitsu |
| R2-2010628 |
Multi-CC simultaneous TCI activation with multi-TRP/panel transmission |
Ericsson |
| R2-2010634 |
Reply LS on multi-CC simultaneous TCI activation with multi-TRP/panel transmission |
Ericsson |
| R2-2010637 |
Correction for CC list operation for TCI state update MAC CE |
Ericsson, Samsung |
| R2-2010760 |
Summary of Offline 101 - MAC corrections for eMIMO |
Samsung |
| R2-2010762 |
Correction to parameter list for beam failure recovery procedure |
Samsung Electronics, ZTE Corporation, Sanechips |
| R2-2010771 |
Reply LS on multi-CC simultaneous TCI activation with multi-TRP/panel transmission |
Ericsson |
| R2-2010772 |
Correction for CC list operation for TCI state update MAC CE |
Ericsson, Samsung |
| R2-2010773 |
38.321 Correction on Enhanced PUCCH Spatial Relation ActivationDeactivation MAC CE |
ZTE Corporation, Sanechips |
| R2-2010774 |
Summary of offline 101 - Way forward on BFR trigger point / BFR MAC CE generation issue |
Samsung |
| R2-2010799 |
Reply LS on multi-CC simultaneous TCI activation with multi-TRP/panel transmission |
Ericsson |
| R2-2010805 |
Correction on BFR MAC CE Generation and Build after Triggering of BFR |
ZTE, Ericsson, Nokia, Samsung |
| R2-2010806 |
Correction for CC list operation for TCI state update MAC CE |
Ericsson, Samsung |
| R2-2010854 |
Reply LS on multi-CC simultaneous TCI activation with multi-TRP/panel transmission |
Ericsson |
| R2-2010855 |
Correction for CC list operation for TCI state update MAC CE |
Ericsson, Samsung |
| R2-2010887 |
Correction for CC list operation for TCI state update MAC CE |
Ericsson, Samsung |
| R2-2010898 |
Reply LS on multi-CC simultaneous TCI activation with multi-TRP/panel transmission |
RAN2 |
| R2-2010900 |
38.321 correction on Enhanced PUCCH Spatial Relation Activation/Deactivation MAC CE |
ZTE Corporation, Sanechips |
| R2-2011203 |
LS on CBRA based Beam Failure Recovery (R1-2009519; contact: Apple) |
RAN1 |
| 6.13.2 |
Control plane corrections |
|
| R2-2009169 |
Clarification to DCI format 1-2 TDRA |
Nokia, Nokia Shanghai Bell |
| R2-2010011 |
Correction on BFD resource on SCell |
Qualcomm Incorporated |
| R2-2010126 |
Correction on HARQ ACK/NACK feedback configuration |
Huawei, HiSilicon |
| R2-2010127 |
Correction on slot based repetition |
Huawei, HiSilicon |
| R2-2010625 |
On number for supported CORESETs |
Ericsson |
| R2-2010636 |
Clarification for multiDCI-MultiTRP-r16 applicability |
Ericsson |
| R2-2010655 |
Correction on slot based repetition |
Huawei, HiSilicon |
| R2-2010775 |
Correction to PDSCH TDRA for DCI 1-2 |
Nokia, Nokia Shanghai Bell |
| R2-2010776 |
Correction on HARQ ACK/NACK feedback configuration |
Huawei, HiSilicon |
| R2-2010777 |
Correction on slot based repetition |
Huawei, HiSilicon |
| R2-2010778 |
On number for supported CORESETs |
Ericsson |
| R2-2010779 |
Clarification for multiDCI-MultiTRP-r16 applicability |
Ericsson |
| R2-2010782 |
Introduction of capability bit for multi-CC simultaneous TCI activation with multi-TRP |
Huawei, HiSilicon |
| R2-2010783 |
Introduction of capability bit for multi-CC simultaneous TCI activation with multi-TRP |
Huawei, HiSilicon |
| R2-2010796 |
Summary of offline 108 - RRC corrections for eMIMO |
Huawei |
| R2-2010800 |
Correction on slot based repetition |
Huawei, HiSilicon |
| R2-2010801 |
Correction on slot based repetition |
Huawei, HiSilicon |
| R2-2010802 |
Capability for slot based repetition |
Huawei, HiSilicon |
| R2-2010807 |
Introduction of capability bit for multi-CC simultaneous TCI activation with multi-TRP |
Huawei, HiSilicon |
| R2-2010808 |
Introduction of capability bit for multi-CC simultaneous TCI activation with multi-TRP |
Huawei, HiSilicon |
| R2-2010885 |
Introduction of capability bit for multi-CC simultaneous TCI activation with multi-TRP |
Huawei, HiSilicon |
| R2-2010886 |
Introduction of capability bit for multi-CC simultaneous TCI activation with multi-TRP |
Huawei, HiSilicon |
| R2-2010888 |
Introduction of capability bit for multi-CC simultaneous TCI activation with multi-TRP |
Huawei, HiSilicon |
| R2-2010889 |
Introduction of capability bit for multi-CC simultaneous TCI activation with multi-TRP |
Huawei, HiSilicon |
| R2-2011014 |
LS on TPMI grouping capability (R1-2009449; contact: vivo) |
RAN1 |
| R2-2011160 |
Summary of offline 108 - RRC corrections for eMIMO - second round |
Huawei |
| R2-2011167 |
Clarification on multipleCORESET |
Ericsson |
| R2-2011168 |
Clarification on multipleCORESET |
Ericsson |
| R2-2011169 |
On number for supported CORESETs |
Ericsson |
| R2-2011232 |
On number for supported CORESETs |
Ericsson |
| R2-2011233 |
Clarification on multipleCORESET |
Ericsson |
| R2-2011234 |
Correction on HARQ ACK/NACK feedback configuration |
Huawei, HiSilicon |
| R2-2011235 |
On number for supported CORESETs |
Ericsson |
| R2-2011236 |
On number for supported CORESETs |
Ericsson |
| R2-2011237 |
Clarification for multipleCORESET |
Ericsson |
| R2-2011238 |
On number for supported CORESETs |
Ericsson |
| R2-2011239 |
Clarification for multipleCORESET |
Ericsson |
| R2-2011281 |
Introduction of capability bit for multi-CC simultaneous TCI activation with multi-TRP |
Huawei, HiSilicon |
| 6.14 |
NR Other R1 WIs |
|
| R2-2008705 |
Reply LS on exchange of information related to SRS-RSRP measurement resource configuration for UE-CLI (R1-2007187; contact: ZTE) |
RAN1 |
| R2-2008729 |
Full slot formats support in TDD UL-DL configuration (R3-205794; contact: Qualcomm) |
RAN3 |
| R2-2010172 |
DRAFT Reply LS on Full slot formats support in TDD UL-DL configuration |
Qualcomm Incorporated |
| R2-2010521 |
Supported slot formats in RAN2 specifications |
Ericsson |
| R2-2010780 |
DRAFT Reply LS on Full slot formats support in TDD UL-DL configuration |
Qualcomm Incorporated |
| R2-2011018 |
Reply LS on full slot formats support in TDD UL-DL (R1-2009505; contact: Qualcomm) |
RAN1 |
| R2-2011161 |
Reply LS on Full slot formats support in TDD UL-DL configuration |
RAN2 |
| 6.14.2 |
Control plane corrections |
|
| R2-2008825 |
Configuration for directional collision handling between reference cell and other cell for half-duplex operation in CA |
Nokia, Nokia Shanghai Bell, Ericsson |
| R2-2008826 |
Missing configuration for half-DuplexTDD-CA-SameSCS-r16 |
Nokia, Nokia Shanghai Bell |
| R2-2010134 |
Discussion on RAN3 LS on full slot format support |
Huawei, HiSilicon |
| R2-2010809 |
LS on half-duplex operation |
RAN2 |
| 6.15 |
NR Other R4 WIs |
|
| R2-2008737 |
LS on additional DC location reporting for intra-band UL CA (R4-2011906; contact: Qualcomm) |
RAN4 |
| R2-2008740 |
LS on clarification for the UE behaviour when UL 7.5kHz shift is optionally supported by a UE (R4-2011746; contact: Apple) |
RAN4 |
| R2-2008741 |
LS on UE capability for PC2 inter-band EN-DC (LTE FDD+NR TDD) (R4-2011787; contact: China Unicom) |
RAN4 |
| R2-2008747 |
Reply LS on CGI reading with autonomous gaps (R4-2012156; contact: ZTE) |
RAN4 |
| R2-2008749 |
LS on number of configurable CSI-RS resources per MO (R4-2012291; contact: Huawei) |
RAN4 |
| R2-2008910 |
Correction of MPE reporting field name |
Lenovo, Motorola Mobility |
| R2-2009164 |
Corrections to MPE reporting |
Nokia, Nokia Shanghai Bell |
| R2-2009165 |
Corrections to inter-node signalling for MPE reporting |
Nokia, Nokia Shanghai Bell |
| R2-2009166 |
Stage-2 description of MPE reporting |
Nokia (Rapporteur) |
| R2-2009167 |
DC location reporting for UL CA |
Nokia, Nokia Shanghai Bell |
| R2-2009168 |
Draft LS reply on DC location reporting |
Nokia, Nokia Shanghai Bell |
| R2-2009245 |
CR to add prerequisite of UL Tx switching capability |
ZTE Corporation, Sanechips |
| R2-2009346 |
38306 CR for the support of EN-DC FDD+TDD HPUE |
China Unicom, Huawei, HiSilicon |
| R2-2009365 |
Increase of the maximum number of configured CSI-RS resources per MO |
CATT |
| R2-2009371 |
Discussion on DC location reporting for intra-band UL CA |
CATT |
| R2-2009466 |
Discussion on UL 7.5kHz shift in NR TDD bands |
Apple |
| R2-2009467 |
UE support on UL 7.5kHz shift in TDD bands – Alt 1 |
Apple |
| R2-2009468 |
UE support on UL 7.5kHz shift in TDD bands – Alt 2 |
Apple |
| R2-2009469 |
UE support on UL 7.5kHz shift in TDD bands – Alt 3 |
Apple |
| R2-2009470 |
UE support on UL 7.5kHz shift in TDD bands |
Apple |
| R2-2009471 |
Draft response LS on UE capability for UL 7.5kHz shift in TDD bands |
Apple |
| R2-2009518 |
Dynamic Reporting of Tx DC Location for UL CA |
Apple |
| R2-2009544 |
NR CA additional spectrum emission requirements |
Nokia, Nokia Shanghai Bell |
| R2-2009690 |
Miscellaneous correction on MPE reporting to 38.321 |
LG Electronics Inc., Ericsson, Apple |
| R2-2009700 |
UE capability for UL 7.5KHz shift in NR TDD with 30KHz SCS |
Ericsson |
| R2-2009701 |
UE behaviour when UL 7.5KHz shift is not supported |
Ericsson |
| R2-2009775 |
On increasing the number of CSI-RS resources for L3 mobility |
Nokia, Nokia Shanghai Bell |
| R2-2009776 |
Draft LS response on increasing the number of CSI-RS resources for L3 mobility |
Nokia, Nokia Shanghai Bell |
| R2-2009777 |
Draft 38331 CR on increasing the number of CSI-RS resources for L3 mobility |
Nokia, Nokia Shanghai Bell |
| R2-2009906 |
38.321 Correction on MPE reporting triggered by the relative threshold |
ZTE Corporation, Sanechips |
| R2-2009907 |
38.331 Correction on relative threshold for MPE configuration |
ZTE Corporation, Sanechips |
| R2-2010048 |
DC location reporting for intra-band UL CA |
Ericsson |
| R2-2010171 |
DC location reporting for intra-band UL CA |
Qualcomm Incorporated |
| R2-2010226 |
support of EN-DC TDD-FDD HPUE |
Huawei, HiSilicon, China Unicom |
| R2-2010227 |
Discussion on supporting 7.5KHz shift for TDD bands |
Huawei, HiSilicon |
| R2-2010228 |
On the signaling for additional DC location reporting |
Huawei, HiSilicon |
| R2-2010289 |
38.331 Correction on relative threshold for MPE configuration |
ZTE Corporation, Sanechips |
| R2-2010358 |
38331 CR on CGI reading with autonomous gaps |
Huawei, HiSilicon |
| R2-2010409 |
Discussion on support of additional DC location reporting for intra-band UL CA |
Samsung Electronics Co., Ltd |
| R2-2010471 |
Discussion on additional DC location reporting for intra-band UL CA |
OPPO |
| R2-2010515 |
Introduction of MPE reporting |
Ericsson |
| R2-2010516 |
MPE for EN-DC, NE-DC, NR-DC and DAPS |
Ericsson |
| R2-2010585 |
38331 CR for CSI-RS-ResourceConfigMobility |
Huawei, HiSilicon |
| R2-2010586 |
38306 CR for supporting a maximum of 192 CSI-RS resources per MO |
Huawei, HiSilicon |
| R2-2010598 |
Correction on T321 for autonomous gap based CGI in FR2 |
ZTE Corporation, Sanechips |
| R2-2010599 |
Correction on T321 for autonomous gap based CGI in FR2 |
ZTE Corporation, Sanechips |
| R2-2010673 |
LS on additional DC location reporting for intra-band UL CA (R4-2011906; contact: Qualcomm) |
RAN4 |
| R2-2010979 |
Discussion on support of additional DC location reporting for intra-band UL CA |
Samsung Electronics Co., Ltd |
| R2-2010981 |
Stage-2 description of MPE reporting |
Nokia (Rapporteur), Ericsson |
| R2-2010983 |
UE behaviour when UL 7.5KHz shift is not supported |
Ericsson |
| R2-2011013 |
Reply LS on number of configurable CSI-RS resources per MO (R1-2009444; contact: LGE) |
RAN1 |
| R2-2011025 |
Summary for Offline [025][R4 NR16] CSI-RS for Mobility |
Huawei |
| R2-2011026 |
38331 CR for CSI-RS-ResourceConfigMobility |
Huawei, HiSilicon, Nokia, Nokia Shanghai Bell |
| R2-2011027 |
38306 CR for supporting a maximum of 192 CSI-RS resources per MO |
Huawei, HiSilicon |
| R2-2011046 |
Summary on [AT112-e][023][R4 NR16] UL 7.5kHz Shift (Apple) |
Apple |
| R2-2011047 |
38331 CR for increasedNumberofCSIRSPerMO |
Huawei, HiSilicon |
| R2-2011066 |
UE behaviour when UL 7.5KHz shift is not supported |
Ericsson, Apple, Nokia, Nokia Shanghai Bell |
| R2-2011134 |
Miscellaneous correction on MPE reporting |
LG Electronics Inc., Ericsson, Apple, Nokia, Nokia Shanghai Bell, Lenovo, Motorola Mobility |
| R2-2011135 |
NR CA additional spectrum emission requirements |
Nokia, Nokia Shanghai Bell |
| R2-2011140 |
Summary of offline 026 Rel-16 miscellaneous RAN4 issues |
Huawei, HiSilicon |
| R2-2011141 |
Removing cross reporting for MPE |
Ericsson, LG Electronics Inc., Nokia, Nokia Shanghai Bell |
| R2-2011207 |
LS on uplink Tx switching (R1-2009676; contact: China Telecom) |
RAN1 |
| 6.16 |
NR Other |
|
| R2-2008722 |
Reply LS on energy efficiency (R3-205657; contact: Ericsson) |
RAN3 |
| R2-2008756 |
LS on mandatory support of full rate user plane integrity protection for 5G (S2-2006181; contact: Qualcomm) |
SA2 |
| R2-2008893 |
Correction to DRX state of SCells in secondary DRX group upon SCell activation |
Qualcomm Incorporated, Ericsson |
| R2-2008894 |
UE capability for DRX state of secondary DRX group upon SCell activation |
Qualcomm Incorporated, Ericsson |
| R2-2008895 |
Configuration and capability signaling for DRX state of secondary DRX group upon SCell activation |
Qualcomm Incorporated, Ericsson |
| R2-2009099 |
Corrections to Active time determination |
Samsung Electronics Co., Ltd |
| R2-2009240 |
Clarify the usage of voiceFallbackIndication for emergency service |
ZTE Corporation, Sanechips |
| R2-2009241 |
CR to clarify the usage of voiceFallbackIndication for emergency service |
ZTE Corporation, Sanechips |
| R2-2009244 |
CR to introduce different SCSs of CSI-RS resource in INM |
ZTE Corporation, Sanechips |
| R2-2009401 |
Clarification on NeedForGap reporting in NR-DC and NE-DC |
MediaTek Inc., ZTE Corporation, Sanechips |
| R2-2009488 |
Discussion on RRC processing delay |
Apple |
| R2-2009489 |
RRC CR on RRC processing delay |
Apple |
| R2-2009604 |
Timer handling for DL segmented RRC message |
Samsung |
| R2-2009605 |
T319 timer handling for DL segmented RRC messages |
Samsung |
| R2-2009606 |
T300 timer handling for DL segmented RRC messages |
Samsung |
| R2-2009812 |
Miscellaneous corrections on overheating assistance information for NR SCG |
ZTE corporation, Sanechips |
| R2-2009849 |
Release with Redirect in 2 steps |
Ericsson |
| R2-2009925 |
On combined RRC procedures |
Nokia, Nokia Shanghai Bell, Ericsson |
| R2-2009926 |
RRC processing delays for combined procedures |
Nokia, Nokia Shanghai Bell, Ericsson |
| R2-2009947 |
Secondary DRX group description is missing |
Ericsson, Qualcomm |
| R2-2009948 |
Clarification for aperiodic CSI and secondary DRX group |
Ericsson, Qualcomm |
| R2-2009949 |
Secondary DRX and architecture options |
Ericsson, Qualcomm |
| R2-2009985 |
Discarding of stored DL RRC message segments when UE transitions to RRC_IDLE |
MediaTek Inc. |
| R2-2010081 |
Correction regarding overheating assistance for SCG |
Samsung Telecommunications |
| R2-2010202 |
Discussion on emergency services in RAN sharing scenario |
Huawei, HiSilicon |
| R2-2010203 |
Clarification on emergency call in RAN sharing scenario |
Huawei, HiSilicon |
| R2-2010204 |
Clarification on emergency call in RAN sharing scenario |
Huawei, HiSilicon |
| R2-2010257 |
New RRC Release cause for inter-RAT cell (re)selection in RRC_INACTIVE |
Huawei, HiSilicon |
| R2-2010258 |
New RRC Release cause for inter-RAT cell (re)selection in RRC_INACTIVE |
Huawei, HiSilicon |
| R2-2010417 |
Discussion on UE behaviours for access barring alleviation |
Google Inc. |
| R2-2010434 |
Clarification on RRC connection fallback handling |
Google Inc. |
| R2-2010448 |
Correction to MAC timer procedures |
Qualcomm Incorporated |
| R2-2010449 |
UE capability for not restarting MAC timers |
Qualcomm Incorporated |
| R2-2010450 |
Configuration and capability signaling for not restarting MAC timers |
Qualcomm Incorporated |
| R2-2010487 |
Miscellaneous corrections on overheating assistance information for NR SCG |
ZTE corporation, Sanechips |
| R2-2010510 |
RRC segmentation for handover and dual connectivity |
Ericsson |
| R2-2010511 |
RRC segmentation for handover and dual connectivity |
Ericsson |
| R2-2010514 |
Full rate UP IP correction |
Ericsson |
| R2-2010527 |
Discussion on band combination selection |
NTT DOCOMO, INC. |
| R2-2010528 |
Optimization for band combination selection |
NTT DOCOMO, INC. |
| R2-2010543 |
UE indication when it no longer experiences overheating |
Ericsson |
| R2-2010547 |
1 bit capbility for gap requirment info for EN-DC |
Qualcomm Incorporated |
| R2-2010548 |
1 bit capbility for gap requirment info for EN-DC |
Qualcomm Incorporated |
| R2-2010549 |
1 bit capbility for gap requirment info for NR |
Qualcomm Incorporated |
| R2-2010550 |
1 bit capbility for gap requirment info for NR |
Qualcomm Incorporated |
| R2-2010551 |
1 bit capbility for gap requirment info for LTE |
Qualcomm Incorporated |
| R2-2010552 |
1 bit capbility for gap requirment info for LTE |
Qualcomm Incorporated |
| R2-2010553 |
gap capability dynamic reporting for NR-DC |
Qualcomm Incorporated |
| R2-2010554 |
gap capability dynamic reporting for NR-DC |
Qualcomm Incorporated |
| R2-2010555 |
NeedForGap for EN-DC |
Qualcomm Incorporated |
| R2-2010556 |
NeedForGap for EN-DC |
Qualcomm Incorporated |
| R2-2010564 |
Supported C-DRX configurations by the network |
Qualcomm Incorporated |
| R2-2010649 |
Optimization for band combination selection over inter-node RRC message (2) |
NTT DOCOMO INC. |
| R2-2010990 |
Reply LS on energy efficiency (S5-205357; contact: Orange) |
SA5 |
| R2-2011072 |
Email report [AT112-e][028][NR TEI16] Misc Corrections I |
Ericsson |
| R2-2011151 |
Release with Redirect for connection resume triggered by NAS |
Ericsson |
| R2-2011152 |
Release with Redirect for connection resume triggered by NAS |
Ericsson |
| R2-2011171 |
Miscellaneous corrections on overheating assistance information for NR SCG |
ZTE corporation, Sanechips |
| R2-2011176 |
Email discussion summary of [029][NR TEI16] Misc Corrections II |
ZTE Corporation |
| R2-2011181 |
Clarification on the indication of eCall over IMS |
Huawei, HiSilicon, Ericsson |
| R2-2011198 |
Clarification for secondary DRX |
Ericsson |
| R2-2011199 |
Full rate UP IP correction |
Ericsson, Deutsche Telekom, Intel Corporation |
| R2-2011200 |
Secondary DRX group description is missing |
Ericsson, Qualcomm |
| R2-2011201 |
[DRAFT] LS on DL RRC segmentation |
Ericsson |
| R2-2011214 |
Email report [AT112-e][028][NR TEI16] Misc Corrections I phase 2 |
Ericsson |
| R2-2011222 |
Correction regarding overheating assistance for SCG |
Samsung Telecommunications |
| R2-2011249 |
Secondary DRX group description is missing |
Ericsson, Qualcomm |
| R2-2011257 |
Clarification on the indication of eCall over IMS |
Huawei, HiSilicon, Ericsson |
| R2-2011258 |
Correction regarding overheating assistance for SCG |
Samsung |
| R2-2011266 |
LS on DL RRC segmentation |
RAN2 |
| R2-2011269 |
Secondary DRX group description is missing |
Ericsson, Qualcomm |
| 7.1.1 |
Cross WI RRC corrections |
|
| R2-2009608 |
Updated consolidated parameter list for Rel-16 LTE |
Samsung |
| R2-2009609 |
Reply LS on updated Rel-16 LTE parameter lists |
RAN2 |
| 7.1.2 |
Feature Lists and UE capabilities |
|
| R2-2008703 |
LS on updated Rel-16 RAN1 UE features list for LTE (R1-2007139; contact: NTT DoCoMo, AT&T) |
RAN1 |
| R2-2008709 |
LS on updated Rel-16 RAN1 UE features lists for LTE (R1-2007329; contact: NTT DoCoMo, AT&T) |
RAN1 |
| R2-2008742 |
LS on Rel-16 updated RAN4 UE features lists for LTE and NR (R4-2011929; contact: CMCC) |
RAN4 |
| R2-2011116 |
LS on updated Rel-16 RAN1 UE features lists for LTE (R1-2009351; contact: NTT DOCOMO, AT&T) |
RAN1 |
| R2-2011191 |
LS on Rel-16 updated RAN4 UE features lists for LTE and NR (R4-2016849; contact: CMCC) |
RAN4 |
| 7.2.1 |
General and Stage-2 corrections |
|
| R2-2010497 |
Support for eDRX cyle beyond 10.24s in RRC_INACTIVE |
LG Electronics UK |
| 7.2.3 |
Connection to 5GC corrections |
|
| R2-2009051 |
Discussion for clarification on SIB acquisition for eMTC UE in RRC_INACTIVE |
ZTE Corporation, Sanechips |
| R2-2009738 |
Correction to the DRX cycle on RRC_INACTIVE for eMTC |
Huawei, HiSilicon |
| R2-2010461 |
Clarification on SIB acquisition for eMTC UE in RRC_INACTIVE |
ZTE Corporation, Sanechips |
| R2-2010816 |
Report of [AT112-e][403][eMTC R16] SIB acquisition for UEs in RRC_INACTIVE (ZTE) |
ZTE (email discussion rapporteur) |
| R2-2010817 |
Correction to the DRX cycle on RRC_INACTIVE for eMTC |
Huawei, HiSilicon |
| 7.2.4 |
MTC UE capabilities corrections |
|
| R2-2009447 |
UE capability for RSS on the same 2 RBs of the MPDCCH narrowband |
Qualcomm Inc, Ericsson |
| R2-2009448 |
RSS and relaxed monitoring capabilities for eMTC |
Qualcomm Inc, Ericsson |
| R2-2009736 |
Addition of missing capabilities for eMTC R16 |
Huawei, HiSilicon |
| R2-2009737 |
Addition of missing capabilities for eMTC R16 |
Huawei, HiSilicon |
| R2-2010818 |
Addition of missing capabilities for eMTC R16 |
Huawei, HiSilicon |
| R2-2010819 |
Addition of missing RSS capability for eMTC |
Huawei, HiSilicon, Qualcomm Inc., Ericsson |
| R2-2010902 |
Addition of missing RSS and relaxed RRM measurement capabilities for eMTC |
Huawei, HiSilicon, Qualcomm Inc., Ericsson |
| 7.3.1 |
General and Stage-2 Corrections |
|
| R2-2008758 |
Reply LS on system support for WUS (S2-2006478; contact: Qualcomm) |
SA2 |
| 7.3.2 |
UE-group wake-up signal (WUS) Corrections |
|
| R2-2009024 |
Discussion for correction on paging narrowband selection for eMTC UE |
ZTE Corporation, Sanechips |
| R2-2009728 |
Clarification on the last used cell for GWUS |
Huawei, HiSilicon |
| R2-2009729 |
Clarification on the last used cell for GWUS |
Huawei, HiSilicon |
| R2-2010057 |
Correction on paging narrowband selection for eMTC UE |
ZTE Corporation, Sanechips |
| R2-2010236 |
Clarification on WUS group set selection |
Ericsson |
| R2-2010907 |
Clarification to the last used cell for (G)WUS |
Huawei, HiSilicon |
| R2-2010908 |
Clarification on WUS group set selection |
Ericsson |
| R2-2010910 |
Report of [AT112-e][305][NBIOT/eMTC R16] Paging narrowband selection for RRC_INACTIVE (ZTE) |
ZTE (email discussion rapporteur) |
| 7.3.3 |
Transmission in preconfigured resources corrections |
|
| R2-2009730 |
Clarification on the reference (N)RSRP for the first TA validation for PUR |
Huawei, HiSilicon |
| R2-2010909 |
Clarification on the reference (N)RSRP for the first TA validation for PUR |
Huawei, HiSilicon |
| 7.3.4 |
Other NB-IoT Specific corrections |
|
| R2-2009733 |
Correction to CP RRC Connection Reestablishment in 5GC |
Huawei, HiSilicon |
| 7.4.1 |
General and Stage-2 Corrections |
|
| R2-2009765 |
Clarification on no DAPS HO in MR-DC |
Nokia, Nokia Shanghai Bell |
| R2-2010207 |
Correction for the definition of DAPS handover (36.300) |
SHARP Corporation |
| R2-2010208 |
Correction for the definition of DAPS handover (38.300) |
SHARP Corporation |
| R2-2010507 |
Clarifications on DAPS and conditional handover for LTE-5GC |
Ericsson |
| 7.4.2 |
DAPS handover Corrections |
|
| R2-2009272 |
Release SCells/SCG configuration during DAPS HO |
Intel Corporation |
| R2-2009275 |
Support of DAPS handover without key change |
Intel Corporation, Ericsson |
| R2-2009276 |
Miscellaneous corrections for Mobility Enhancements |
Intel Corporation (Rapporteur), Ericsson |
| R2-2009380 |
Discussion on SCells and SCG release in DAPS HO |
ZTE Corporation, Sanechips, Ericsson |
| R2-2009381 |
Clarification on SCells and SCG release in DAPS HO - 38.300 |
ZTE Corporation, Sanechips, Ericsson |
| R2-2009382 |
Clarification on SCells and SCG release in DAPS HO - 36.300 |
ZTE Corporation, Sanechips, Ericsson |
| R2-2009383 |
Clarification on no support of multi-TRP with DAPS HO - 38.331 |
ZTE Corporation, Sanechips, Ericsson |
| R2-2009384 |
Clarification on no support of multi-TRP with DAPS HO - 38.300 |
ZTE Corporation, Sanechips, Ericsson |
| R2-2009534 |
Correction on Source Cell Group and Source SpCell on DAPS |
CATT,Ericsson |
| R2-2009535 |
Corrections on DAPS in 36.331 |
CATT,Ericsson |
| R2-2009559 |
Handling of SCells and mTRP during DAPS HO |
Qualcomm Incorporated |
| R2-2009607 |
Release of mTRP operation before DAPS handover |
Samsung |
| R2-2009654 |
Handling of expiry of dataInacticityTimer for DAPS |
NEC |
| R2-2009767 |
On how to release SCells when DAPS HO is configured |
Nokia, Nokia Shanghai Bell |
| R2-2009768 |
Draft 38331 CR SCells during DAPS HO |
Nokia, Nokia Shanghai Bell |
| R2-2009769 |
Draft 36331 CR SCells during DAPS HO |
Nokia, Nokia Shanghai Bell |
| R2-2009770 |
Prohibiting simultaneous DAPS and multi-TRP operation |
Nokia, Nokia Shanghai Bell |
| R2-2010105 |
Clarification of SCells, mTRP, and DC during DAPS HO |
Qualcomm Incorporated |
| R2-2010209 |
Potential security issue on DAPS handover with key change failure |
SHARP Corporation |
| R2-2010210 |
[Draft] LS to SA3 on security handling for DAPS handover |
SHARP Corporation |
| R2-2010294 |
Correction on RLF handling in DAPS |
Huawei, HiSilicon |
| R2-2010295 |
Correction on RLF handling in DAPS |
Huawei, HiSilicon |
| R2-2010297 |
Correction on reestablishRLC for DAPS |
Huawei, HiSilicon |
| R2-2010328 |
DAPS HO without security key change |
LG Electronics Inc. |
| R2-2010435 |
Correction on DAPS |
OPPO |
| R2-2010498 |
Restriction on PHR for DAPS |
Ericsson, China Telecom, LG Electronics Inc., Nokia, Nokia Shanghai-Bell, MediaTek, Vivo, CATT |
| R2-2010499 |
RLF in source during DAPS |
Ericsson |
| R2-2010501 |
Handling of dataInactivityTimer for DAPS |
Ericsson |
| R2-2010504 |
Miscellaneous mobility-related corrections |
Ericsson, ETRI |
| R2-2010505 |
Release source cell configuration at DAPS handover |
Ericsson |
| R2-2010506 |
DAPS handover for bearers configured with NR PDCP |
Ericsson |
| R2-2010639 |
Discussion on source release indication |
Huawei, HiSilicon |
| R2-2010640 |
Discussion on releasing source MCG SCells and mTRP |
Huawei, HiSilicon |
| R2-2010727 |
[AT112-e][213][MOB] DAPS RRC corrections |
Ericsson |
| R2-2010728 |
Miscellaneous corrections for DAPS (LTE) |
Ericsson, ETRI, CATT |
| R2-2010729 |
Miscellaneous corrections for DAPS (NR) |
Ericsson, Lenovo, Motorola Mobility, CATT, ITRI |
| R2-2010747 |
Clarification on no support of CA or DC with DAPS |
ZTE Corporation, Sanechips, Ericsson |
| R2-2010748 |
Clarification on no support of CA, DC or multi-TRP with DAPS |
ZTE Corporation, Sanechips, Ericsson |
| R2-2010749 |
Clarification on no support of CA or DC with DAPS |
ZTE Corporation, Sanechips, Ericsson |
| R2-2010750 |
Clarification on no support of CA, DC or multi-TRP with DAPS |
ZTE Corporation, Sanechips, Ericsson |
| 7.4.3 |
UE capability corrections |
|
| R2-2009188 |
Clarifications to LTE DAPS capabilities |
Nokia, Nokia Shanghai Bell |
| R2-2010298 |
Correction on LTE DAPS UE capability |
Huawei, HiSilicon |
| R2-2010299 |
Correction on LTE DAPS UE capability |
Huawei, HiSilicon |
| R2-2010502 |
Introducing power sharing for DAPS handover |
Ericsson, Qualcomm |
| R2-2010503 |
Introducing power sharing for DAPS handover |
Ericsson, Qualcomm |
| R2-2010681 |
Introducing power sharing for DAPS handover |
Ericsson, Qualcomm, Huawei |
| R2-2010682 |
Introducing power sharing for DAPS handover |
Ericsson, Qualcomm, Huawei |
| R2-2011089 |
Introducing power sharing for DAPS handover |
Ericsson, Qualcomm, Huawei |
| R2-2011299 |
Introducing power sharing for DAPS handover |
Ericsson, Qualcomm, Huawei |
| 7.4.4 |
Other corrections |
|
| R2-2010641 |
Cell selection upon RRCConnectionReestablishment |
Samsung R&D Institute UK |
| R2-2010645 |
Miscellaneous corrections on LTE CHO procedures |
Samsung R&D Institute UK |
| 7.5 |
LTE Other WIs |
|
| R2-2008704 |
LS on Updates to TS 36.300 on terrestrial broadcast (R1-2007154; contact: Qualcomm) |
RAN1 |
| R2-2008907 |
Corrections to UE capabilities |
Lenovo, Motorola Mobility (Rapporteur) |
| R2-2008908 |
Corrections to UE capabilities and SIB25 |
Lenovo, Motorola Mobility, Ericsson |
| R2-2009385 |
Correction on T312 timer information |
ZTE Corporation, Sanechips |
| R2-2009433 |
Clarification to Fallback band combination definition |
Nokia, Nokia Shanghai Bell |
| R2-2009446 |
CP length and reference signal for MBSFN with sub-carrier spacing of 0.375 KkHz and 2.5 kKHz |
Qualcomm Inc |
| R2-2009603 |
Minor changes collected by Rapporteur |
Samsung |
| R2-2009802 |
Miscellaneous Stage-2 corrections |
Nokia (rapporteur), NEC, Lenovo, Motorola Mobility, Intel Corporation, ZTE, Sanechips, Ericsson |
| R2-2010713 |
Miscellaneous Stage-2 corrections |
Nokia (rapporteur), NEC, Lenovo, Motorola Mobility, Intel Corporation, ZTE, Sanechips, Ericsson |
| R2-2010758 |
CP length and reference signal for MBSFN with sub-carrier spacing of 0.375 kHz and 2.5 kHz |
Qualcomm Incorporated |
| R2-2010989 |
LS on QoE Measurement Collection (S5-205347; contact: Ericsson) |
SA5 |
| R2-2011086 |
Minor changes collected by Rapporteur |
Samsung |
| R2-2011099 |
Corrections to UE capabilities |
Lenovo, Motorola Mobility (Rapporteur) |
| 8.1.1 |
Organizational, Requirements, Scope and Architecture |
|
| R2-2008751 |
Reply LS on RAN impact of FS_5MBS Study (RP-202086; contact: Huawei) |
RAN |
| R2-2008755 |
LS on RAN impact of FS_5MBS Study (S2-2006044; contact: Huawei) |
SA2 |
| R2-2008768 |
Reply LS on RAN impact of FS_5MBS Study (SP-200884; contact: Huawei) |
SA |
| R2-2008791 |
Discussion on Requirement and Architecture of MBS |
CATT |
| R2-2008865 |
Considerations on Protocol stack and network architecture |
OPPO |
| R2-2008929 |
Discussioin on the protocol stack for NR MBS |
CHENGDU TD TECH LTD. |
| R2-2009036 |
NR Multicast Vs Broadcast comparison and Radio Bearer Architecture aspects |
Qualcomm Inc |
| R2-2009196 |
MBS L2 Architecture, user plane and control plane |
Intel Corporation |
| R2-2009303 |
MBS Protocol Architecture and Logical Channel Aggregation |
Futurewei |
| R2-2009334 |
Updated NR MBS workplan |
Huawei, CMCC, HiSilicon |
| R2-2009335 |
Discussion on SA2 LS on RAN impact of FS_5MBS Study |
Huawei, HiSilicon |
| R2-2009336 |
Draft reply LS to SA2 on RAN impact of FS_5MBS Study |
Huawei, HiSilicon |
| R2-2009337 |
Summary of Email discussion Post111-e-904 MBS L2 Architecture |
Huawei, HiSilicon |
| R2-2009343 |
38.300 running CR for NR MBS |
Huawei, HiSilicon |
| R2-2009668 |
Framework for NR MBS Broadcast and Multicast services |
Lenovo, Motorola Mobility |
| R2-2009740 |
L2 architecture for NR MBS |
ZTE, Sanechips |
| R2-2009822 |
draft_Reply LS on RAN impact of FS_5MBS Study |
ZTE, Sanechips |
| R2-2009883 |
Security for PTP and PTM switching |
Sony |
| R2-2009954 |
SA2 questions about RRC state transitions for multicast |
Ericsson |
| R2-2010064 |
On Stage-2 aspects and overview of NR MBS |
Samsung |
| R2-2010214 |
General considerations on NR MBS |
vivo |
| R2-2010234 |
Consideration of control plane aspects for NR MBS |
Kyocera |
| R2-2010411 |
Discussion on user-plane channel structure for MBS |
LG Electronics Inc. |
| R2-2011022 |
Summary of [AT112-e][036][MBS] SA2 LS on MBS |
Huawei, HiSilicon |
| R2-2011133 |
Draft reply LS to SA2 on RAN impact of FS_5MBS Study |
Huawei, HiSilicon |
| R2-2011170 |
[DRAFT] Reply LS on RAN impact of FS_5MBS Study |
Huawei, HiSilicon |
| R2-2011271 |
Reply LS on RAN impact of FS_5MBS Study |
RAN2 |
| 8.1.2.1 |
Reliability |
|
| R2-2008792 |
Reliability Enhancement for PTM Transmission |
CATT |
| R2-2008866 |
Discussion on reliability for MBS reception |
OPPO |
| R2-2008932 |
Consideration on reliability for NR MBS |
CHENGDU TD TECH LTD. |
| R2-2009034 |
NR Multicast PTM bearer RLC AM mode operation |
Qualcomm Inc, British Telecom, Kyocera, FirstNet, AT&T |
| R2-2009126 |
HARQ operation for NR MBS reliable transmission |
MediaTek Inc. |
| R2-2009154 |
Discussion on reliability of MBS service |
Spreadtrum Communications |
| R2-2009197 |
MBS service reliability improvement |
Intel Corporation |
| R2-2009304 |
ARQ of PTM with Logical Channel Aggregation |
Futurewei |
| R2-2009313 |
PDCP Operation for MBS |
Nokia, Nokia Shanghai Bell |
| R2-2009338 |
Reliability enhancement for NR MBS |
Huawei, HiSilicon |
| R2-2009494 |
Consideration on MBS transmission reliability |
Apple |
| R2-2009575 |
Reliable MBS Transmission |
Sharp |
| R2-2009600 |
Reliability Enhancements for NR MBS |
Samsung |
| R2-2009612 |
Reliability of NR MBS |
NEC |
| R2-2009741 |
Consideration on MBS reliability guarantee |
ZTE, Sanechips |
| R2-2009879 |
On HARQ and RLC for 5G MBS reliability |
Lenovo, Motorola Mobility |
| R2-2009961 |
Reliability for multicast operation |
Ericsson |
| R2-2010160 |
On reliability enhancement for NR multicast and broadcast |
Convida Wireless |
| R2-2010215 |
Discussion reliability for RRC_CONNECTED UEs |
vivo |
| R2-2010382 |
Consideration on Reliability Enhancement for MBS |
CMCC |
| R2-2010412 |
Discussion on reliability improvement and UL feedback in NR multicast |
LG Electronics Inc. |
| R2-2010643 |
Discussion on UE mode in CONNECTED states |
TD Tech |
| 8.1.2.2 |
Dynamic PTM PTP switch with service continuity |
|
| R2-2008793 |
Open Issues on Dynamic PTM and PTP Switch |
CATT |
| R2-2008867 |
Dynamic PTM and PTP switching with service continuity |
OPPO |
| R2-2008930 |
Dynamic switch between PTM and PTP with service continuity |
CHENGDU TD TECH LTD. |
| R2-2008989 |
Dynamic switch between PTM and PTP for service continuity |
Intel Corporation |
| R2-2009037 |
Enhancements for supporting loss less PTM PTP switching |
Qualcomm Inc |
| R2-2009103 |
Consideration on PTP/PTM switching |
Shanghai Jiao Tong University |
| R2-2009127 |
Dynamic PTM-PTP switch |
MediaTek Inc. |
| R2-2009128 |
NR MBS Radio Bearer Structure |
MediaTek Inc. |
| R2-2009155 |
Discussion on dynamic PTM PTP switch |
Spreadtrum Communications |
| R2-2009305 |
Service Continuity during Dynamic PTM/PTP Switch with Logical Channel Aggregation |
Futurewei |
| R2-2009314 |
MBS split bearer configuration and PTP/PTM switching |
Nokia, Nokia Shanghai Bell |
| R2-2009339 |
Support of dynamic switch between PTP and PTM |
Huawei, HiSilicon |
| R2-2009440 |
Dynamic PTP PTM switch |
LG Electronics Inc. |
| R2-2009495 |
PTM PTP switch with MBS service continuity |
Apple |
| R2-2009576 |
Dynamic switch between PTP and PTM |
Sharp |
| R2-2009601 |
PTM PTP Switching and MBS Bearer Type |
Samsung |
| R2-2009613 |
Service Continuity for Connected mode UE |
NEC |
| R2-2009614 |
Simultaneous transmission of multicast/unicast |
NEC |
| R2-2009641 |
Discussion on the counting scheme for dynamically switching PTM and PTP |
ITRI |
| R2-2009673 |
Clarification on the dynamic switching in MAC |
Beijing Xiaomi Mobile Software |
| R2-2009742 |
Dynamic mode switching for NR MBS |
ZTE, Sanechips |
| R2-2009880 |
5G MBS dynamic switch between PTP and PTM with service continuity |
Lenovo, Motorola Mobility |
| R2-2009959 |
PTM to PTP Dynamic Switch |
Ericsson |
| R2-2010139 |
Dynamic PTM/PTP Switching |
Convida Wireless |
| R2-2010216 |
Dynamic PTM PTP switch for RRC Connected UE |
vivo |
| R2-2010383 |
Discussion on Dynamic PTM PTP switch with service continuity |
CMCC |
| 8.1.2.3 |
Mobility with Service continuity |
|
| R2-2008794 |
Open Issues on Mobility with Service Continuity |
CATT |
| R2-2008868 |
Discussion on mobility with MBS Service continuity |
OPPO |
| R2-2008931 |
Discussion on mobility with service continuity |
CHENGDU TD TECH LTD. |
| R2-2008945 |
Reliability and latency handling during NR multicast mobility |
TCL Communication Ltd. |
| R2-2008990 |
MBS service continuity in mobility |
Intel Corporation |
| R2-2009035 |
NR Multicast Broadcast mobility enhancements with service continuity |
Qualcomm Inc |
| R2-2009054 |
HO for NR MBS |
MediaTek Inc. |
| R2-2009156 |
Discussion on sevice continuity during mobility |
Spreadtrum Communications |
| R2-2009340 |
Service continuity during inter-cell mobility |
Huawei, HiSilicon |
| R2-2009444 |
MBS service continuity |
LG Electronics Inc. |
| R2-2009461 |
General Considerations on Mobility with Service Continuity |
Samsung R&D Institute India |
| R2-2009496 |
Mobility with MBS service continuity |
Apple |
| R2-2009674 |
UE assistance information for connected mobility |
Beijing Xiaomi Mobile Software |
| R2-2009743 |
Consideration on lossless handover for NR MBS |
ZTE, Sanechips |
| R2-2009881 |
Connected Mode Mobility with Service Continuity |
Lenovo, Motorola Mobility |
| R2-2009884 |
PTP/PTM MRB and RLM |
Sony |
| R2-2009960 |
Mobility for NR MBS |
Ericsson |
| R2-2010143 |
MBS Mobility Management |
Nokia, Nokia Shanghai Bell |
| R2-2010217 |
MBS Service Continuity for RRC Connected UE |
vivo |
| R2-2010384 |
Discussion on Mobility with Service Continuity |
CMCC |
| R2-2010385 |
Summary of [Post111-e][905][MBS] Connected Mode Mobility with Service Continuity (CMCC) |
CMCC |
| 8.1.2.4 |
Other |
|
| R2-2008795 |
Discussion on Miscellaneous Issues |
CATT |
| R2-2008874 |
Discussion on group-based scheduling for MBS |
OPPO |
| R2-2008934 |
RAN2 related aspects for NR MBS |
CHENGDU TD TECH LTD. |
| R2-2009315 |
Miscellaneous Aspects of MBS |
Nokia, Nokia Shanghai Bell |
| R2-2009320 |
Discussion on RAN level QoS handling for MBS service area |
TCL Communication Ltd. |
| R2-2009341 |
General aspects for NR MBS |
Huawei, HiSilicon |
| R2-2009445 |
Consideration on properties of NR for multicastbroadcast |
LG Electronics Inc. |
| R2-2009497 |
MBS reception in CONNECTED state |
Apple |
| R2-2009537 |
Group Scheduling and Multiplexing Aspects |
Samsung R&D Institute India |
| R2-2009962 |
Aspects of Group Sscheduling |
Ericsson |
| R2-2010218 |
Control of transmission area and group scheduling |
vivo |
| R2-2010386 |
Discussion on Beam Level MBS Deployment |
CMCC |
| 8.1.3 |
Idle and Inactive mode UEs |
|
| R2-2008796 |
Summary of Email Discussion Post111-e906 MBS Idle mode support |
CATT |
| R2-2008797 |
Further Discussion on MBS Idle Mode Support |
CATT, CBN |
| R2-2008869 |
Discussion on MBS reception of idle or inactive mode UE |
OPPO |
| R2-2008933 |
NR MBS for RRC_IDLE/RRC_INACTIVE UE |
CHENGDU TD TECH LTD. |
| R2-2008940 |
IDLE/INACTIVE UE support for NR MBS |
TCL Communication Ltd. |
| R2-2008991 |
MBS support for IDLE and INACTIVE states |
Intel Corporation |
| R2-2009038 |
NR Multicast-Broadcast services and configuration for UEs in different RRC states |
Qualcomm Inc |
| R2-2009157 |
MBS for Idle and Inactive mode UE |
Spreadtrum Communications |
| R2-2009283 |
Discussion on NR MBS structure allowing service for idle UEs |
Futurewei |
| R2-2009319 |
Consideration on MBS support in idle/inactive modes |
ETRI |
| R2-2009342 |
RRC states for MBS reception and Idle/Inactive UE support |
Huawei, HiSilicon |
| R2-2009441 |
MBS in IDLEI NACTIVE |
LG Electronics Inc. |
| R2-2009498 |
MBS reception in IDLE/INACTIVE state |
Apple |
| R2-2009555 |
IDLE and INACTIVE state UE operation |
Nokia, Nokia Shanghai Bell |
| R2-2009579 |
Discussion on introducing counting and UE interest indication mechanism for UE in idle/inactive mode |
China Unicom |
| R2-2009611 |
IDLE /IN_ACTIVE UE support of MBS |
NEC |
| R2-2009744 |
Support of Idle and Inactive mode UEs for NR MBS |
ZTE, Sanechips |
| R2-2009902 |
Open issues on MBS idle mode support |
MediaTek Inc. |
| R2-2009953 |
MBS reception in Idle and Inactive mode |
Ericsson |
| R2-2010078 |
RRC IDLE/ INACTIVE aspects of NR MBS |
Samsung |
| R2-2010145 |
On NR multicast and broadcast for RRC_IDLE/RRC_INACTIVE UEs |
Convida Wireless |
| R2-2010219 |
Discussion on Idle and Inactive mode UEs |
vivo |
| R2-2010387 |
Discussion on Idle and Inactive UE MBS Reception |
CMCC |
| R2-2010644 |
Discussion on MBS support for UE in IDLE and INACTIVE states |
TD Tech |
| 8.2.2 |
Efficient activation / deactivation mechanism for one SCG and SCells |
|
| R2-2008870 |
Discussion on SCG suspension or deactivation |
OPPO |
| R2-2008920 |
Considerations on fast (de)active of Scell |
KDDI Corporation |
| R2-2009150 |
Discussion on efficient activation mechanism for one SCG |
Spreadtrum Communications |
| R2-2009246 |
Further consideration on SCG activation and deactivation |
ZTE Corporation, Sanechips |
| R2-2009259 |
On Support of Activation/Deactivation for SCG |
InterDigital |
| R2-2009284 |
Further discuss the issues with SCG fast activation |
Futurewei |
| R2-2009357 |
Efficient Activation/Deactivation Mechanism for SCG |
CATT |
| R2-2009439 |
Discussion on SCG suspension |
MediaTek Inc. |
| R2-2009531 |
Open items on SCG deactivation feature |
Apple |
| R2-2009547 |
On fast deactivation and activation of one SG and SCells |
Nokia, Nokia Shanghai Bell |
| R2-2009590 |
Discussion on efficient deactivation mechanism for the SCG |
China Unicom |
| R2-2009814 |
SCG deactivation upon SCG addition |
NEC |
| R2-2009867 |
On SCG deactivatoin and activation |
Lenovo, Motorola Mobility |
| R2-2009913 |
Discussion on efficient SCG activation/deactivation |
China Telecommunications |
| R2-2009942 |
Signalling for Rel-17 efficient SCG de-activation/re-activation |
Intel Corporation |
| R2-2010062 |
Efficient SCG (de)activation |
Ericsson |
| R2-2010087 |
Progressing SCG deactivation and resumption for R17 |
Samsung Telecommunications |
| R2-2010123 |
[Post111-e][919][eDCCA] Efficient activation deactivation of SCG Discussion on SCG deactivation and activation |
Huawei |
| R2-2010124 |
Discussion on SCG deactivation and activation |
Huawei, HiSilicon |
| R2-2010132 |
Efficient SCG activation/deactivation in MR-DC |
Qualcomm Incorporated |
| R2-2010231 |
Signalling for SCG activation |
SHARP Corporation |
| R2-2010283 |
Efficient SCG Activation mechanism |
LG Electronics |
| R2-2010290 |
Activation and deactivation mechanism for SCG and SCells |
vivo |
| R2-2010372 |
Considerations on SCG activation or deactivation |
CMCC |
| R2-2010683 |
Progressing SCG deactivation and resumption for R17 |
Samsung Telecommunications |
| R2-2010733 |
[AT112-e][230][eDCCA] Progressing FFS points of efficient SCG activation and deactivation (Huawei) |
Huawei |
| 8.2.3 |
Conditional PSCell change / addition |
|
| R2-2009088 |
Conditional PSCell change / addition |
vivo |
| R2-2009158 |
CPC configuration number restriction |
Spreadtrum Communications |
| R2-2009260 |
Coexistence of CHO and CPC |
InterDigital |
| R2-2009285 |
CPAC failure handling discussio |
Futurewei |
| R2-2009358 |
Discussion on Further CPAC Enhancements |
CATT |
| R2-2009359 |
Introduction of CPA and MN Initiated Inter-SN CPC |
CATT |
| R2-2009360 |
Summary of [Post111-e][920][eDCCA] Conditional PSCell Change and Addition (CATT) |
CATT |
| R2-2009379 |
Discussion on conditional PSCell addition/change |
ZTE Corporation, Sanechips |
| R2-2009475 |
Discussion on conditional PSCell change and addition |
Apple |
| R2-2009592 |
Discussion on inter-SN conditional PSCell change (SN initiated) |
China Unicom |
| R2-2009596 |
Discussion on conditional PSCell change and addition |
OPPO |
| R2-2009771 |
On Rel-17 Conditional PSCell Addition and Change (CPAC) |
Nokia, Nokia Shanghai Bell |
| R2-2009815 |
Conditional PSCell addition procedure |
NEC |
| R2-2009816 |
Framework of Inter-SN Conditional PSCell change |
NEC |
| R2-2009868 |
Issues on inter-SN CPC |
Lenovo, Motorola Mobility |
| R2-2010003 |
Conditional PSCell Change / Addition |
Ericsson |
| R2-2010088 |
Progressing conditional configuration for R17 |
Samsung Telecommunications |
| R2-2010125 |
Discussion on support of conditional PSCell change/addition |
Huawei, HiSilicon |
| R2-2010130 |
Configuration of Conditional PSCell addition/change |
Qualcomm Incorporated |
| R2-2010248 |
Discussion on SN initiated CPC and CPAC Execution |
ETRI |
| R2-2010282 |
Considerations of CPAC in Rel-17 |
LG Electronics |
| R2-2010373 |
Discussions about CPAC procedures |
CMCC |
| R2-2010529 |
Regarding inter MN-SN signaling design for Conditional PSCell Addition |
Intel Corporation |
| R2-2010626 |
Further consideration for Conditional PSCell addition and change |
NTT DOCOMO INC. |
| R2-2010734 |
[AT112-e][231][eDCCA] Progressing conditional reconfiguration for SN initiated inter-SN CPC (CATT) |
CATT |
| R2-2010850 |
LS on Conditional PSCell Aaddition/Change agreements |
RAN2 |
| 8.3 |
Multi SIM |
|
| R2-2008831 |
Discussion on various scenarios of UE switching from network for activities on another network |
China Telecommunications |
| R2-2008832 |
Support of UE capabilities coordination for Dual Tx/Dual Rx Multi-USIM UEs |
China Telecommunications |
| 8.3.1 |
Organizational, Requirements and Scope |
|
| R2-2008754 |
LS on System support for Multi-USIM devices (S2-2006037; contact: Intel) |
SA2 |
| R2-2009325 |
Summary of [Post111-e][917][Multi-SIM] Multi-Sim |
vivo |
| R2-2009885 |
Discussion on Multi SIM |
Sony, Convida Wireless |
| R2-2009943 |
[DRAFT] Reply LS on System support for Multi-USIM devices |
Intel Corporation |
| R2-2010689 |
Reply to LS S2-2006037 on System support for Multi-USIM devices (S3-202687; contact: Nokia) |
SA3 |
| R2-2010737 |
Summary of [AT112-e][240][Multi-SIM] Reply LS to SA2 (Intel) |
Intel |
| R2-2010738 |
Draft reply LS on System support for Multi-USIM devices |
Intel |
| R2-2011241 |
Reply LS on System support for Multi-USIM devices |
RAN2 |
| 8.3.2 |
Paging collision avoidance |
|
| R2-2008871 |
Discussion on paging collision issue for multi-SIM |
OPPO |
| R2-2008955 |
Discussion on Paging Collision Avoidance |
CATT |
| R2-2009264 |
Analysis of solutions for paging collision |
Nokia, Nokia Shanghai Bell |
| R2-2009326 |
Evaluation on Paging Collision Solutions |
vivo |
| R2-2009505 |
MUSIM Page Collision Avoidance |
Apple |
| R2-2009538 |
Effective Solution for Paging Collision Avoidance |
Samsung R&D Institute India |
| R2-2009556 |
Preventing paging collisions for Multi-SIM |
Qualcomm Incorporated |
| R2-2009622 |
Consideration on the Paging Collision |
ZTE Corporation, Sanechips |
| R2-2009659 |
Consideration on Multi-SIM |
China Telecom |
| R2-2009692 |
Definition and solution for paging collision, RRC Inactive, SI change |
Lenovo, Motorola Mobility |
| R2-2009739 |
Guidance for SA2 on Solution #16 for Key Issue 2 |
VODAFONE Group Plc |
| R2-2009779 |
Discussion of the paging collision problem |
Xiaomi Communications |
| R2-2009780 |
Guidance for SA2 on Solution #16 for Key Issue 2 |
VODAFONE Group Plc |
| R2-2009786 |
Support for Multi-SIM Devices - Paging Collision |
MediaTek Inc. |
| R2-2009851 |
On Paging Collision Avoidance |
Huawei, HiSilicon |
| R2-2009940 |
“Effective” solution for paging collision avoidance |
Intel Corporation |
| R2-2009971 |
Response to SA2 LS S2-2006037: Paging Repetition in RAN and UE Implementation-based solution aspects |
VODAFONE Group Plc |
| R2-2010284 |
Consideration of Paging Collision Avoidance |
LG Electronics |
| R2-2010427 |
UE indication of paging collision for Multi-SIM |
ASUSTeK |
| R2-2010445 |
Considerations for Paging Collision for Multi-SIM UEs |
Charter Communications, Inc |
| R2-2010482 |
Consideration on slice specific cell selection and reselection |
ZTE corporation, Sanechips |
| R2-2010534 |
Paging collision avoidance |
Ericsson |
| R2-2010596 |
RAN2 Impacts of Multi-USIM Paging |
Futurewei Technologies |
| 8.3.3 |
UE notification on network switching for multi-SIM |
|
| R2-2008872 |
Discussion on graceful leaving and busy indication |
OPPO |
| R2-2008956 |
Discussion on UE Notification on Network Switching |
CATT |
| R2-2009265 |
Scenarios and Impact analysis for Switching Notification |
Nokia, Nokia Shanghai Bell |
| R2-2009327 |
UE notification on network switching for multi-SIM |
vivo |
| R2-2009328 |
Discussion on Busy Indication Procedure |
vivo |
| R2-2009506 |
MUSIM Network Switching |
Apple |
| R2-2009557 |
Switching between two links for Multi-SIM |
Qualcomm Incorporated |
| R2-2009623 |
Consideration on the Switching Notification Procedure |
ZTE Corporation, Sanechips |
| R2-2009658 |
RRC-based coordinated switch for multi-USIM UE |
NEC |
| R2-2009781 |
Discussion of the UE switching problem |
Xiaomi Communications |
| R2-2009787 |
Support for Multi-SIM Devices - Notification upon Network Switching |
MediaTek Inc. |
| R2-2009856 |
Switching Notification in MUSIM |
Lenovo, Motorola Mobility |
| R2-2009941 |
Regarding UE notification on network switching for multi-SIM |
Intel Corporation |
| R2-2010246 |
On coordinated switch from NW for MUSIM device |
Huawei, HiSilicon |
| R2-2010286 |
SIM Switching Handling in MUSIM |
LG Electronics |
| R2-2010350 |
Discussion on switching mechanism for multi-SIM |
Samsung Electronics Co., Ltd |
| R2-2010428 |
Mechanism for UE to notify network switching |
ASUSTeK |
| R2-2010477 |
Network Switching for Multi-SIM UEs |
Charter Communications, Inc |
| R2-2010481 |
Consideration on the slice specific RACH configuration |
ZTE corporation, Sanechips |
| R2-2010544 |
Graceful leaving for a MultiSIM device |
Ericsson |
| R2-2010620 |
RAN2 impacts of multi-SIM UE notifications on network switching |
Futurewei Technologies |
| 8.3.4 |
Paging with service indication |
|
| R2-2008873 |
Discussion on paging cause for multi-SIM |
OPPO |
| R2-2008957 |
Discussion on Paging with Service Indication |
CATT |
| R2-2009153 |
Discussion on the open issues of paging transmission |
Spreadtrum Communications |
| R2-2009266 |
On RAN impacts for on paging cause |
Nokia, Nokia Shanghai Bell |
| R2-2009507 |
MUSIM Paging with Service Indication |
Apple |
| R2-2009558 |
Paging prioritization and response for MUSIM |
Qualcomm Incorporated |
| R2-2009624 |
Consideration on the Paging Cause |
ZTE Corporation, Sanechips |
| R2-2009791 |
Support for Multi-SIM Devices - Paging Cause |
MediaTek Inc. |
| R2-2009852 |
Discussion on the paging with service indication |
Huawei, HiSilicon |
| R2-2010250 |
Discussion on support of paging cause for multi-SIM |
Samsung Electronics Co., Ltd |
| R2-2010285 |
Consideration on Paging Cause Indication |
LG Electronics |
| R2-2010416 |
Discussion of the paging cause support for MUSIM |
Xiaomi Communications |
| R2-2010535 |
Introduction of a Paging cause indication |
Ericsson |
| R2-2010739 |
[AT112-e][241][Multi-SIM] Network switching sc]enarios (vivo) |
vivo |
| 8.4.1 |
Organizational, Requirements and Scope |
|
| R2-2009291 |
Updated workplan for Rel-17 IAB |
Qualcomm Incorporated (WI Rapporteur) |
| 8.4.2 |
Enhancements to improve topology-wide fairness, multi-hop latency and congestion mitigation |
|
| R2-2008848 |
Consideration on topology-wide fairness, multi-hop latency and congestion mitigation |
CATT |
| R2-2009006 |
Discussion on the fairness enforcement for IAB |
Fujitsu |
| R2-2009073 |
Report from email discussion [Post111-e][902][eIAB] |
Samsung Electronics GmbH |
| R2-2009089 |
On topology-wide fairness |
Samsung Electronics GmbH |
| R2-2009090 |
Enhancements to multi-hop latency and congestion mitigation |
Samsung Electronics GmbH |
| R2-2009200 |
Discussion on Topology-wide fairness and flow control enhancement |
Intel Corporation |
| R2-2009261 |
On multi-hop latency and congestion mitigation |
InterDigital |
| R2-2009293 |
Simulations on fairness support in IAB topology |
Qualcomm Incorporated |
| R2-2009329 |
Discussion on congestion, RLF, latency and fairness handling |
vivo |
| R2-2009332 |
Multi-hop scheduling and local routing enhancements for IAB |
AT&T |
| R2-2009388 |
Discussion on topology-wide fairness multi-hop latency and congestion mitigation |
ZTE, Sanechips |
| R2-2009509 |
Fairness metrics in multi-hop eIAB networks |
Apple |
| R2-2009651 |
Enhancements for topology-wide fairness, multi-hop latency and congestion mitigation |
Huawei, HiSilicon |
| R2-2009667 |
Discussion on topology-wide fairness, multi-hop latency and congestion mitigation |
LG Electronics |
| R2-2009798 |
Hop-by-hop flow control in uplink |
Nokia, Nokia Shanghai Bell |
| R2-2009886 |
Topology-wide fairness enhancements |
Sony |
| R2-2010099 |
Rel. 17 IAB enhancements for fairness, multi-hop latency reduction, and congestion mitigation |
Futurewei Technologies |
| R2-2010159 |
On Topology-wide Fairness, Multi-hop Latency and Congestion Mitigation |
Ericsson |
| R2-2010489 |
Discussion on congestion mitigation enhancements |
ETRI |
| R2-2011060 |
Discussion summary - [AT112-e][030][eIAB] |
nnSamsung |
| R2-2011061 |
Report from email discussion [Post111-e][902][eIAB] Enhancements to improve topology-wide fairness, multi-hop latency and congestion mitigation (Samsung) |
Samsung Electronics GmbH |
| R2-2011142 |
Discussion summary - [AT112-e][030][eIAB] |
nnSamsung |
| 8.4.3 |
Topology adaptation enhancements |
|
| R2-2008849 |
Consideration on Topology adaptation enhancements |
CATT |
| R2-2009007 |
CHO for UE or IAB-MT on migration |
Fujitsu |
| R2-2009201 |
Enhancements to establish efficient topologies and backhaul failure recovery |
Intel Corporation |
| R2-2009262 |
On IAB Topology Adaptation |
InterDigital |
| R2-2009292 |
Report of email discussion on topology adaptation enhancements RAN2 scope |
Qualcomm Incorporated |
| R2-2009330 |
Consideration of Inter-CU IAB Migration |
vivo |
| R2-2009387 |
Considerations on topology adaptation enhancements |
ZTE, Sanechips |
| R2-2009422 |
On topology adaptation enhancements |
Nokia, Nokia Shanghai Bell |
| R2-2009508 |
Better Cell Selection for eIAB nodes for improved topology adaptation |
Apple |
| R2-2009610 |
Topology optimization in IAB |
NEC |
| R2-2009652 |
Consideration of topology adaptation enhancement for R17-IAB |
Huawei, HiSilicon |
| R2-2009887 |
Topology adaptation enhancements in IAB |
Sony |
| R2-2010137 |
Consideration on avoiding RLF recovery at former descendent nodes |
Sharp |
| R2-2010158 |
On WI scope and solutions for topology adaptation and inter-CU migration |
Ericsson |
| R2-2010233 |
Consideration of topology adaptation enhancements for eIAB |
Kyocera |
| R2-2010441 |
BAP Packet Duplication and BH RLF Indication Enhancements |
LG Electronics France |
| R2-2010490 |
RAN2 impacts of Rel.17 IAB topology adaptation enhancements |
Futurewei Technologies |
| R2-2010670 |
On topology adaptation enhancements |
Nokia, Nokia Shanghai Bell |
| R2-2010671 |
On topology adaptation enhancements |
Nokia, Nokia Shanghai Bell |
| R2-2011040 |
Report from [AT112-e][031][eIAB] Topology Adaptation – PART A |
Qualcomm (Moderator) |
| R2-2011125 |
Report from [AT112-e][031][eIAB] Topology Adaptation – PART B |
Qualcomm (Email discussion rapporteur) |
| 8.4.4 |
Duplexing enhancements, RAN2 scope |
|
| R2-2009091 |
Views on duplexing enhancements |
Samsung Electronics GmbH |
| R2-2009389 |
Discussion on duplexing enhancement |
ZTE, Sanechips |
| R2-2009653 |
Duplexing enhancements for R17 IAB |
Huawei, HiSilicon |
| 8.5.1 |
Organizational |
|
| R2-2008720 |
LS on propagation delay compensation enhancements (R1-2007446; contact: Huawei) |
RAN1 |
| R2-2009754 |
Updated Work Plan for NR IIoT/URLLC |
Nokia |
| 8.5.2 |
Enhancements for support of time synchronization |
|
| R2-2008855 |
Discussion on enhancements for support of time synchronization |
Huawei, HiSilicon |
| R2-2008856 |
Draft Reply LS on propagation delay compensation enhancements |
Huawei, HiSilicon |
| R2-2008880 |
Propagation Delay Compensation Enhancements |
Ericsson |
| R2-2008972 |
Propagation Delay Compensation for TSN |
Qualcomm Incorporated |
| R2-2009060 |
Further consideration on time synchronization and PDC in TSN |
ZTE Corporation, Sanechips, China Southern Power Grid Co., Ltd |
| R2-2009118 |
On propagation delay compensation |
MediaTek Inc. |
| R2-2009270 |
Enhancements for Propagation Delay Compensation and Mobility |
Intel Corporation |
| R2-2009561 |
Consideration of time synchronization enhancement for TSN |
OPPO |
| R2-2009672 |
Mobility related issues for the propagation delay compensation |
Beijing Xiaomi Mobile Software |
| R2-2009755 |
Summary of email discussion [Post111-e][924][R17 URLLC/IIoT] Propagation delay for TSN (Nokia) |
Nokia, Nokia Shanghai Bell |
| R2-2009756 |
[DRAFT] Reply LS on propagation delay compensation enhancements |
Nokia, Nokia Shanghai Bell |
| R2-2009757 |
Discussion on propagation delay compensation mechanisms |
Nokia, Nokia Shanghai Bell |
| R2-2009865 |
Considerations on time synchronization enhancement |
Lenovo, Motorola Mobility |
| R2-2009915 |
Discussion on enhancements for TSN time synchronization |
China Telecommunications |
| R2-2010173 |
Mobility aspects of time synchronization |
Sequans Communications |
| R2-2010211 |
Discussion on the propagation delay compensation |
vivo |
| R2-2010381 |
Enhancements for support of time synchronization for TSN |
CMCC |
| R2-2010413 |
Discussion on propagation delay compensation for support of time synchronization |
LG Electronics Inc. |
| R2-2010523 |
RAN2 Aspects on Timing Synchronization |
Samsung |
| R2-2010532 |
Uplink time synchronization |
NTT DOCOMO, INC. |
| R2-2010837 |
Reply LS on propagation delay compensation enhancements |
RAN2 |
| 8.5.3 |
Uplink enhancements for URLLC in unlicensed controlled environments |
|
| R2-2008853 |
Discussion about uplink enhancements for URLLC in unlicensed controlled environment |
Huawei, HiSilicon |
| R2-2008859 |
Co-existence of NR-U and IIOT in R16 |
CATT |
| R2-2008860 |
Protocol selection for IIoT on unlicensed spectrum |
CATT |
| R2-2008881 |
Harmonizing UL CG enhancements in NR-U and URLLC |
Ericsson |
| R2-2008974 |
CG Harmonization in Unlicensed Controlled Environment |
Qualcomm Incorporated |
| R2-2008976 |
Uplink enhancements for URLLC in unlicensed controlled environments |
Intel Corporation |
| R2-2009117 |
On configured grant harmonization |
MediaTek Inc. |
| R2-2009501 |
Potential UL enhancements for URLLC in unlicensed environments |
Apple |
| R2-2009562 |
Consideration on URLLC over NRU |
OPPO |
| R2-2009598 |
Enhancements for URLLC in unlicensed controlled environments |
Lenovo, Motorola Mobility |
| R2-2009758 |
Uplink CG Harmonization for NR-U and URLLC |
Nokia, Nokia Shanghai Bell |
| R2-2009900 |
Considerations in unlicensed URLLC |
Sony Europe B.V. |
| R2-2009912 |
Considerations on the harmonization of enhanced configured grant on shared spectrum channel |
ZTE Corporation, Sanechips |
| R2-2009914 |
Discussion on CG harmonization for IIoT in unlicensed spectrum |
Google Inc. |
| R2-2010110 |
IIoT operation in unlicensed controlled environments |
InterDigital |
| R2-2010212 |
Harmonizing CG enhancements in NR-U and URLLC/IIoT |
vivo |
| R2-2010374 |
Discussion on CG harmonization for URLLC in unlicensed controlled environments |
CMCC |
| R2-2010437 |
Consideration on timers for URLLC/IIoT in unlicensed controlled environments |
III |
| R2-2010439 |
Harmonized support of IIOT on unlicensed band |
LG Electronics Inc. |
| R2-2010524 |
Uplink Enhancements for Unlicensed Spectrum |
Samsung |
| R2-2010836 |
[AT112e][501][IIoT]: Summary of URLLC in unlicensed controlled environment |
Qualcomm |
| 8.5.4 |
RAN enhancements based on new QoS |
|
| R2-2008854 |
Discussion on RAN enhancements based on new QoS related parameters |
Huawei, HiSilicon |
| R2-2008861 |
RAN enhancement based on New QoS |
CATT |
| R2-2008882 |
RAN enhancements based on new QoS related parameters |
Ericsson |
| R2-2008985 |
RAN Enhancements to Support New QoS Parameters for TSN |
Intel Corporation |
| R2-2009062 |
New QoS related parameters in TSN |
ZTE Corporation, Sanechips, China Southern Power Grid Co., Ltd |
| R2-2009130 |
U-plane aspect for RAN enhancement to support new QoS |
Fujitsu |
| R2-2009179 |
Concept and use of survival timer |
Samsung Electronics GmbH |
| R2-2009563 |
Consideration on RAN enhancement based on new QoS |
OPPO |
| R2-2009671 |
RAN impacts of the IIOT QoS parameters |
Beijing Xiaomi Mobile Software |
| R2-2009759 |
RAN Enhancement for Survival Time |
Nokia, Nokia Shanghai Bell |
| R2-2009870 |
Discuss on the mechanism to guarantee the survival time |
Lenovo, Motorola Mobility |
| R2-2010111 |
Enhancements based on new QoS requirements |
InterDigital |
| R2-2010213 |
Discussion on IIOT QoS impacts in RAN |
vivo |
| R2-2010375 |
Discussion on the support of RAN enhancement for new QoS parameters |
CMCC |
| R2-2010438 |
Discussion on RAN enhancements based on Survival Time |
III |
| R2-2010444 |
Support of determinstic IIOT Traffic |
LG Electronics UK |
| R2-2010692 |
LS on Use of Survival Time for Deterministic Applications in 5GS (S2-2007880; contact: Nokia) |
SA2 |
| R2-2010838 |
Reply LS on Use of Survival Time for Deterministic Applications in 5GS |
RAN2 |
| 8.6.1 |
Organizational |
|
| R2-2009189 |
Small Data] Agreeable details of RRC-based solution (RACH and CG) |
Rapporteur (ZTE) |
| R2-2009967 |
Report of [Post111-e][926][SmallData] ContextFetch_email |
Ericsson (rapporteur) |
| R2-2010839 |
LS to RAN3 on small data transmission |
RAN2 |
| R2-2010841 |
LS on physical layer aspects of small data transmission |
RAN2 |
| 8.6.2 |
Security aspects |
|
| R2-2008958 |
Discussion on the Security for Small Data Transmission |
vivo |
| R2-2008992 |
Security aspect for SDT |
Intel Corporation |
| R2-2009012 |
Security aspects for small data transmission in inactive state |
OPPO |
| R2-2009366 |
Security aspects on SDT |
CATT |
| R2-2009490 |
Security aspect on SDT procedure |
Apple |
| R2-2009920 |
Security aspects of SDT |
Nokia, Nokia Shanghai Bell |
| R2-2009931 |
Discussion about security aspects for small data transmission |
Huawei, HiSilicon |
| R2-2009991 |
Draft LS on Need of MAC-I for UE authentication |
NEC Telecom MODUS Ltd. |
| 8.6.3 |
Control plane aspects |
|
| R2-2008959 |
Duscussion on RRC-Controlled Small Data Transmission |
vivo |
| R2-2008993 |
SDT control plane procedures and failure handling |
Intel Corporation |
| R2-2009013 |
Discussion on Control plane aspects for small data transmission |
OPPO |
| R2-2009055 |
RRC-less SDT over CG |
MediaTek Inc., Apple |
| R2-2009095 |
Control Plane Aspects of SDT |
Samsung Electronics Co., Ltd |
| R2-2009131 |
Open issue in [Post111-e][926]: TAT handling |
Fujitsu |
| R2-2009132 |
Identified issue in [Post111-e][926]: CA and PDCP CA duplication |
Fujitsu |
| R2-2009151 |
Discussion on the general aspects for small data transmission |
Spreadtrum Communications |
| R2-2009190 |
Control plane aspects of SDT |
ZTE Corporation, Sanechips |
| R2-2009316 |
Discussion on RRC procedure for small data transmission |
SHARP Corporation |
| R2-2009344 |
Timer configuration for SDT failure detection |
ETRI |
| R2-2009347 |
Differentiation and triggering of SDT procedure |
Potevio |
| R2-2009367 |
Considerations on general aspects and subsequent SDT |
CATT |
| R2-2009460 |
Anchor relocation for Small Data Transmission |
LG Electronics Inc. |
| R2-2009491 |
Control plane aspects on SDT procedure |
Apple |
| R2-2009643 |
Discussion on how to handle cell reselection during T319 for the case of SDT |
ITRI |
| R2-2009656 |
Control plane issues for SDT |
NEC |
| R2-2009675 |
Discussion on the RRC-less SDT |
Beijing Xiaomi Mobile Software |
| R2-2009873 |
Analysis on RA selection and RNAU |
Lenovo, Motorola Mobility |
| R2-2009875 |
Consideration on RRC-less SDT and subsequent data transmission |
Lenovo, Motorola Mobility |
| R2-2009888 |
Discussion on context fetch, anchor relocation and subsequent SDT in NR |
Sony |
| R2-2009919 |
SDT control plane aspects for RACH based schemes |
Nokia, Nokia Shanghai Bell |
| R2-2009930 |
SDT aspects common for RACH-based and CG-based SDT scheme |
Huawei, HiSilicon |
| R2-2009966 |
RRC aspects for SDT |
Ericsson |
| R2-2009978 |
Support of RRC-less SDT |
NEC Telecom MODUS Ltd. |
| R2-2010008 |
Control plane aspects on NR small data transmission |
Qualcomm Incorporated |
| R2-2010109 |
Small data transmission failure and cell reselection |
InterDigital |
| R2-2010388 |
SDT type selection and switch procedure |
CMCC |
| R2-2010429 |
Discussion on subsequent small data transmission |
ASUSTeK |
| 8.6.4 |
Aspects specific to RACH based schemes |
|
| R2-2008960 |
Supporting Small Data Transmission via RA Procedure |
vivo |
| R2-2008994 |
RACH selection and User plane aspects with and without anchor relocation |
Intel Corporation |
| R2-2009014 |
Discussion on RACH based small data transmission |
OPPO |
| R2-2009056 |
RA-based SDT |
MediaTek Inc. |
| R2-2009096 |
Criteria for performing 2 step or 4 step RACH based SDT |
Samsung Electronics Co., Ltd |
| R2-2009097 |
RACH configuration for Small Data Transmission |
Samsung Electronics Co., Ltd |
| R2-2009119 |
Timer issues for subsequent data transmissions |
PANASONIC R&D Center Germany |
| R2-2009152 |
Discussion on small data transmission for RACH-based scheme |
Spreadtrum Communications |
| R2-2009191 |
RACH based small data transmission |
ZTE Corporation, Sanechips |
| R2-2009193 |
Context fetch and data forwarding for SDT |
ZTE Corporation, Sanechips |
| R2-2009368 |
Analysis on SDT without Context relocation |
CATT |
| R2-2009457 |
RACH-based Small Data Transmission |
LG Electronics Inc. |
| R2-2009492 |
Context fetch procedure for SDT |
Apple |
| R2-2009646 |
Discussion on RA-based Small Data Transmission |
TCL Communication Ltd. |
| R2-2009657 |
Subsequent data transmission for SDT |
NEC |
| R2-2009799 |
Details on RACH specific schemes |
Nokia, Nokia Shanghai Bell |
| R2-2009872 |
The basic principle for small data transmissions |
Lenovo, Motorola Mobility |
| R2-2009889 |
Details of RA-based schemes for SDT in NR |
Sony |
| R2-2009963 |
Details of RACH based SDT |
Ericsson |
| R2-2009965 |
Subsequent transmissions after initial SDT |
Ericsson |
| R2-2010006 |
Discussion on RACH based NR small data transmission |
Qualcomm Incorporated |
| R2-2010106 |
RACH-based SDT selection and configuration |
InterDigital |
| R2-2010232 |
2-step RACH and 4-step RACH selection criteria for SDT |
Xiaomi |
| R2-2010280 |
Small data transmission with RA-based scheme |
Huawei, HiSilicon |
| R2-2010281 |
Small data transmission with CG-based scheme |
Huawei, HiSilicon |
| R2-2010389 |
Some consideration on RACH based scheme |
CMCC |
| R2-2010390 |
Anchor relocation and context fetch |
CMCC |
| R2-2010430 |
Data forwarding without UE DRB configuration |
ASUSTeK |
| R2-2010431 |
Discussion on initiating SDT based on radio condition |
ASUSTeK |
| 8.6.5 |
Aspects specific to CG based schemes |
|
| R2-2008935 |
Handling of subsequent small data transmission in RRC_INACTIVE |
PANASONIC R&D Center Germany |
| R2-2008961 |
Supporting Small Data Transmission via CG configuration |
vivo |
| R2-2008995 |
Handling of Configured grant for SDT |
Intel Corporation |
| R2-2009015 |
Discussion on CG based small data transmission |
OPPO |
| R2-2009057 |
CG-based SDT |
MediaTek Inc. |
| R2-2009094 |
Configured Grant based Small Data Transmission |
Samsung Electronics Co., Ltd |
| R2-2009192 |
Configured grant based small data transmission |
ZTE Corporation, Sanechips |
| R2-2009345 |
SDT handling in RRC_INACTIVE state |
ETRI |
| R2-2009350 |
Discussion on aspects specific to CG based SDT |
Nokia, Nokia Shanghai Bell |
| R2-2009369 |
Analysis on SDT Procedures using CG |
CATT |
| R2-2009458 |
Coexistence of CG and RACH configuraiton for SDT |
LG Electronics Inc. |
| R2-2009459 |
CG resources for Small Data Transmission |
LG Electronics Inc. |
| R2-2009493 |
CG based SDT procedure |
Apple |
| R2-2009649 |
TAT maintenance for CG based SDT |
ITL |
| R2-2009874 |
Consideration on CG based small data transmission |
Lenovo, Motorola Mobility |
| R2-2009890 |
Details of CG-based schemes for SDT in NR |
Sony |
| R2-2009964 |
Details of CG based SDT |
Ericsson |
| R2-2009973 |
Discussion on CG-based Small Data Transmissions |
NEC Telecom MODUS Ltd. |
| R2-2010007 |
Discussion on CG based NR small data transmission |
Qualcomm Incorporated |
| R2-2010107 |
CG-based SDT selection and configuration |
InterDigital |
| R2-2010108 |
Beam selection and maintenance for CG-based SDT |
InterDigital |
| R2-2010391 |
Consideration on CG based SDT |
CMCC |
| R2-2010432 |
Association between Pre-configured PUSCH resources and beam |
ASUSTeK |
| 8.7.1 |
Organizational |
|
| R2-2008760 |
LS on Direct Discovery and Relay in SA2 (S2-2006587; contact: Oppo) |
SA2 |
| R2-2008926 |
[Draft] Reply LS on Direct Discovery and Relay |
CATT |
| R2-2008939 |
Work planning of R17 SL relay |
OPPO |
| R2-2010676 |
[Draft] Reply LS on Direct Discovery and Relay |
OPPO |
| R2-2010693 |
LS on SA2 progress on UE-to-Network Relay and UE-to-UE Relay (S2-2007945; contact: OPPO) |
SA2 |
| R2-2010856 |
TR 38.836, v0.2.0 |
OPPO |
| R2-2010862 |
[Draft] Reply LS on Direct Discovery and Relay |
OPPO |
| R2-2010883 |
Reply LS on Direct Discovery and Relay |
RAN2 |
| 8.7.2 |
Scope, requirements, and scenarios |
|
| R2-2008779 |
Left issues on Scenarios for sidelink relay |
OPPO |
| R2-2008921 |
Further Clarification on the Scenarios for NR Sidelink Relay |
CATT |
| R2-2009584 |
Further discussion on scope and scenarios of SL relay |
vivo |
| R2-2009693 |
Coverage Extension using Relays |
Lenovo, Motorola Mobility |
| R2-2009694 |
QoS support when using Relays |
Lenovo, Motorola Mobility |
| R2-2010658 |
Scenarios for NR sidelink relay |
LG Electronics Inc. |
| R2-2010869 |
Summary of [AT112-e][610][Relay] RRC states for L2 relay |
vivo (Rapporteur) |
| R2-2010984 |
Summary for AI_8.7.2 Scope requirements and scenarios |
vivo |
| R2-2011004 |
Summary for AI_8.7.2 Scope requirements and scenarios |
vivo |
| R2-2011262 |
Summary of [AT112-e][610][Relay] RRC states for L2 relay |
vivo (Rapporteur) |
| 8.7.3.1 |
Protocol stacks and procedures |
|
| R2-2008777 |
Left issues on CP procedure for L2 U2N Relay |
OPPO |
| R2-2008922 |
On-demand SI Delivery for Remote UE |
CATT |
| R2-2008962 |
Discussion on remaining issues of L3 relay |
Qualcomm Incorporated |
| R2-2008964 |
Discussion on remaining issues of L2 relay |
Qualcomm Incorporated |
| R2-2008966 |
RRC state and essential RRC procedures in L2 U2N relay |
Qualcomm Incorporated |
| R2-2008983 |
Open aspects of L2 relaying |
Intel Corporation |
| R2-2009030 |
Discussion on remaining issues on L2 relay architecture |
ZTE Corporation, Sanechips |
| R2-2009033 |
Discussion on Remaining issues on L3 relay |
ZTE Corporation, Sanechips |
| R2-2009122 |
Email Report of Post111-e 627 Relay Remaining issues on L2 architecture |
MediaTek Inc. |
| R2-2009123 |
Adaptation layer for PC5 at L2 UE-to-Network Relay |
MediaTek Inc. |
| R2-2009124 |
Overhead in N3IWF based L3 relaying architecture |
MediaTek Inc. |
| R2-2009144 |
Remaining issues on the adaptation layer for Layer-2 Relay |
Spreadtrum Communications |
| R2-2009202 |
Control Plane Aspects for UE to NW Relays |
InterDigital |
| R2-2009203 |
Connection Establishment and Maintenance for L2 Relays |
InterDigital |
| R2-2009206 |
Discussion on L2 Relay Architecture and QoS |
InterDigital |
| R2-2009230 |
RAN2 impacts introduced by Layer 2 SL relay |
Ericsson |
| R2-2009302 |
QoS Control with Sidelink Relay |
Futurewei |
| R2-2009525 |
Discussion on data forwarding mechanisms for Layer 2 UE-to-UE Relay |
Apple |
| R2-2009526 |
Discussion on RRC_INACTIVE remote UE |
Apple |
| R2-2009585 |
Open issues on Layer-2 relay |
vivo |
| R2-2009660 |
L2 relaying open issues |
Samsung Electronics GmbH |
| R2-2009661 |
Need for relaying of on-demand SI |
Samsung Electronics GmbH |
| R2-2009720 |
Discussion on L3 UE-to-NW relay architecture |
Ericsson |
| R2-2009891 |
SL L2 architectrure |
Sony |
| R2-2009901 |
Protocol stack design for U2N relay and U2U relay case |
Lenovo, Motorola Mobility |
| R2-2009939 |
Discussion on L2 based UE-to-Network |
Nokia, Nokia Shanghai Bell |
| R2-2010129 |
Needed Information in Adaptation Layer Header for L2 UE-to-UE Relay |
Convida Wireless |
| R2-2010344 |
Remaining issues on protocol stacks and procedures for L2 relay |
Huawei, HiSilicon |
| R2-2010345 |
NAS transmission and QoS management in L3 U2N relay |
Huawei, HiSilicon |
| R2-2010870 |
Summary of [AT112-e][611][Relay] Open issues on L2 relay |
Huawei |
| R2-2010871 |
Email discussion summary of [612][NR17] Open issues on L3 relay (Qualcomm) |
Qualcomm Incorporated |
| R2-2011114 |
Email discussion summary of [612][NR17] Open issues on L3 relay (Qualcomm) |
Ericsson |
| 8.7.3.2 |
Service continuity |
|
| R2-2008780 |
Left issues on Service continuity for L2 U2N relay |
OPPO |
| R2-2008923 |
Further Clarification on the L2 Service Continuity |
CATT |
| R2-2008967 |
Remaining issues on the mobility procedures for L2 relay |
Qualcomm Incorporated |
| R2-2009031 |
Discussion on Service continuity |
ZTE Corporation, Sanechips |
| R2-2009068 |
L3 relay enhancements to improve path switching |
Nokia, Nokia Shanghai Bell |
| R2-2009125 |
Service Continuity for L2 Relay and L3 Relay |
MediaTek Inc. |
| R2-2009145 |
Discussion on service continuity for Layer-2 UE-to-Network Relay |
Spreadtrum Communications |
| R2-2009171 |
Service continuity via L3 UE-to-Network relaying |
Samsung Electronics |
| R2-2009177 |
Service Continuity Scenarios and AS-Layer Procedures |
Fraunhofer HHI, Fraunhofer IIS |
| R2-2009271 |
Further details on Service Continuity for Relaying |
Intel Corporation |
| R2-2009301 |
Service Continuity with Sidelink Relay |
Futurewei |
| R2-2009476 |
Discussion on service continuity for layer 2 UE to NW relay |
Apple |
| R2-2009586 |
Service continuity for L2 and L3 relay |
vivo |
| R2-2009721 |
Service continuity procedure and scenarios for sidelink relay |
Ericsson |
| R2-2009938 |
Service Continuity for UE2UE Relay |
Nokia, Nokia Shanghai Bell |
| R2-2010329 |
Clarification of remote UE mobility |
ETRI |
| R2-2010346 |
Summary email discussion [621][Relay] of Service continuity |
Huawei, HiSilicon |
| R2-2010469 |
Discussion on service continuity |
Xiaomi communications |
| R2-2010588 |
Service continuity for SL relay |
LG Electronics Inc. |
| R2-2010659 |
Service continuity for Remote UE |
LG Electronics Inc. |
| 8.7.3.3 |
Relay selection |
|
| R2-2008924 |
Further Discussion on NR Sidelink Relay Selection and Reselection |
CATT |
| R2-2008987 |
Further details on relay reselection |
Intel Corporation |
| R2-2009029 |
Discussion on Relay initiation and (re-)selection |
ZTE Corporation, Sanechips |
| R2-2009069 |
Discussion on relay selection and reselection |
Nokia, Nokia Shanghai Bell |
| R2-2009148 |
Discussion on relay selection and reselcetion |
Spreadtrum Communications |
| R2-2009172 |
Consideration on relay reselection criteria |
Samsung Electronics |
| R2-2009176 |
Relay (re)selection enhancement |
MediaTek Inc. |
| R2-2009205 |
Relay Selection and Reselection |
InterDigital |
| R2-2009229 |
Remaining aspects for relay selection and reselection |
Ericsson |
| R2-2009523 |
Summary Report of [Post111-e][622][Relay] Relay selection and reselection |
Apple |
| R2-2009588 |
SL-RSRP and SD-RSRP comparioson and additional criterion for relay (re-)selection |
vivo |
| R2-2009634 |
Considerations on relay selection and reselection |
KT Corp. |
| R2-2009857 |
Relay reselection in the failure case |
Lenovo, Motorola Mobility |
| R2-2009892 |
SL Relay selection |
Sony |
| R2-2009972 |
NR Sidelink Relay (Re-)Selection Criterion and Procedure |
Fraunhofer IIS, Fraunhofer HHI |
| R2-2010005 |
Relay reselection based on discovery |
Kyocera |
| R2-2010347 |
Remaining issues on relay selection and reselection |
Huawei, HiSilicon |
| R2-2010652 |
PC5 link failure handling for NR sidelink relay |
LG Electronics Inc. |
| 8.7.3.4 |
Other |
|
| R2-2008778 |
Left issues on QoS, Security and L23 comparison |
OPPO |
| R2-2009650 |
View on Paging Option 2 in L2 relay |
ITL |
| R2-2009858 |
Considerations on the UE-to-Network relay and UE-to-UE relay case |
Lenovo, Motorola Mobility |
| R2-2010104 |
Release procedure for SL Relaying support |
Intel Corporation |
| 8.7.4 |
Discovery model/procedure for sidelink relaying |
|
| R2-2008802 |
Discussion on AS layer protocol of discovery message for SL relay |
OPPO |
| R2-2008815 |
Summary of [Post111-e][623][Relay]Remaining issues on relay discovery (rapporteur) |
OPPO |
| R2-2008925 |
Discussion on discovery message |
CATT |
| R2-2008965 |
Remaining issues on discovery and relay (re)selection |
Qualcomm Incorporated |
| R2-2008977 |
Further details on SL discovery for relaying |
Intel Corporation |
| R2-2009032 |
Discussion on relay discovery and link management |
ZTE Corporation, Sanechips |
| R2-2009149 |
Discussion on remaining issues on relay discovery |
Spreadtrum Communications |
| R2-2009173 |
Sidelink relay discovery open issue |
Samsung Electronics |
| R2-2009204 |
Discovery Procedure for SL Relays |
InterDigital |
| R2-2009228 |
Remaining aspects for discovery |
Ericsson |
| R2-2009524 |
Discussion on remaining issues on NR Sidelink Relay discovery |
Apple |
| R2-2009587 |
Remaining issues of sidelink relay discovery procedure |
vivo |
| R2-2009633 |
Considerations on discovery for sidelink relay |
KT Corp. |
| R2-2009638 |
Discussion on differentiation of discovery message |
SHARP Corporation |
| R2-2009970 |
NR Sidelink Relaying Discovery |
Fraunhofer IIS, Fraunhofer HHI |
| R2-2009994 |
Discovery resources for sidelink relaying |
Kyocera |
| R2-2010046 |
Discussion on relay discovery model and procedure |
Nokia, Nokia Shanghai Bell |
| R2-2010331 |
On relay discovery |
MediaTek Inc. |
| R2-2010348 |
Remaining issues on relay discovery |
Huawei, HiSilicon |
| R2-2010349 |
Discussion on the discovery aspects related to SA2 LS S2-2006587 |
Huawei, HiSilicon |
| R2-2010467 |
Discussion on scenario regarding non SL relay capable gNB |
Xiaomi communications |
| R2-2010660 |
Remaining issues on discovery for NR sidelink relay |
LG Electronics Inc. |
| R2-2010661 |
Summary of [Post111-e][623][Relay]Remaining issues on relay discovery (rapporteur) |
OPPO |
| 8.8.1 |
Organizational |
|
| R2-2008732 |
LS on Enhancement of RAN Slicing (R3-205802; contact: Qualcomm) |
RAN3 |
| R2-2008759 |
LS on Cell Configuration within TA/RA to Support Allowed NSSAI (S2-2006526; contact: ZTE) |
SA2 |
| R2-2009669 |
Considerations on scenarios and solution space of RAN slicing enhancements |
Lenovo, Motorola Mobility |
| R2-2010183 |
Discussion on restricting the rate per UE per network slice |
Huawei, HiSilicon |
| R2-2010184 |
Draft reply LS on restricting the rate per UE per network slice |
Huawei |
| R2-2010364 |
Revised Work Plan for RAN Slicing |
CMCC, ZTE |
| R2-2010365 |
Draft TR 38.832 |
CMCC, ZTE |
| R2-2010366 |
Report of [Post111-e][916][Slicing] Open issues for RAN slicing |
CMCC |
| R2-2010488 |
Reply LS on Cell Configuration within TA/RA to Support Allowed NSSAI |
Qualcomm Incorporated |
| R2-2010646 |
Draft reply LS on Cell Configuration within TA/RA to Support Allowed NSSAI |
ZTE corporation, Sanechips |
| R2-2010688 |
LS on Cell Configuration within TA/RA to Support Allowed NSSAI (C1-206760; contact: Nokia) |
CT1 |
| R2-2010694 |
LS on restricting the rate per UE per network slice (S2-2007946; contact: Nokia) |
SA2 |
| R2-2010695 |
LS Reply on Enhancement of RAN Slicing (S2-2008240; contact: ZTE) |
SA2 |
| R2-2010987 |
[DRAFT] Reply LS on restricting the rate per UE per network slice |
Nokia |
| R2-2011102 |
Summary of [AT112-e][250][Slicing] LS replies to SA2 and RAN3 (Nokia) |
Nokia |
| R2-2011104 |
Reply LS on LS restricting the rate per UE per network slice |
RAN2 |
| 8.8.2 |
Slice based cell reselection under network control |
|
| R2-2008857 |
Considerations on slice aware cell priority |
KDDI Corporation |
| R2-2008917 |
Slice based Cell Reselection under Network Control |
CATT |
| R2-2008949 |
Cell (re)selection based on preferred frequency(s) per slice |
Beijing Xiaomi Software Tech |
| R2-2008950 |
Deployment scenarios of RAN slicing based on SA2 LSout |
Beijing Xiaomi Software Tech |
| R2-2008963 |
Further discussion on RAN slicing enhancement |
Qualcomm Incorporated |
| R2-2009067 |
Considerations for Slice-based cell (re)selection |
Nokia, Nokia Shanghai Bell |
| R2-2009143 |
Discussion on slice based cell reselection |
Spreadtrum Communications |
| R2-2009174 |
Slice information for cell reselection |
Samsung Electronics |
| R2-2009198 |
Consideration for slice based cell (re)selection |
Intel Corporation |
| R2-2009288 |
5G RAN Slicing Framework During Cell Selection / Reselection Phases |
MITRE Corporation, DoD, NTIA |
| R2-2009473 |
Discussion on slice based cell selection and re-selection |
Apple |
| R2-2009536 |
Discussion on slice based cell reselection under network control |
China Unicom |
| R2-2009542 |
Consideration on slice-based cell (re)selection |
OPPO |
| R2-2009644 |
Assistant information to enable UE fast access network slice |
ITRI |
| R2-2009689 |
Remaining issues on slice-based (re)-selection |
vivo |
| R2-2009807 |
Consideration on slice specific cell selection and reselection |
ZTE corporation, Sanechips |
| R2-2009979 |
Evaluation of Access delay to slice |
Ericsson |
| R2-2009986 |
Solutions for fast access to slice |
Ericsson |
| R2-2010063 |
Cell selection and reselection for RAN slicing |
Google |
| R2-2010065 |
Discussion on Network Slicing’s Impact on Cell (Re-)Selection |
Convida Wireless |
| R2-2010181 |
Slice based Cell (re)selection under network control |
Huawei, HiSilicon |
| R2-2010222 |
Further discussion on how to decide intended slice for idle mobility |
LG Electronics UK |
| R2-2010367 |
Discussion on SA2 LS and solutions for slice-based cell reselection |
CMCC |
| 8.8.3 |
Slice based RACH configuration or access barring |
|
| R2-2009175 |
RACH configuration for RAN slicing |
Samsung Electronics |
| R2-2009199 |
Consideration of Slice based RACH |
Intel Corporation |
| R2-2009423 |
RACH prioritisation for slices |
Nokia, Nokia Shanghai Bell |
| R2-2009474 |
Discussion on slice based RACH and cell barring |
Apple |
| R2-2009543 |
Consideration on slice-based RACH |
OPPO |
| R2-2009688 |
Remaining issues on RACH and service continuity |
vivo |
| R2-2009806 |
Consideration on the slice specific RACH configuration |
ZTE corporation, Sanechips |
| R2-2009974 |
RACH enhancements to enable UE fast access to the intended slice |
NEC Telecom MODUS Ltd. |
| R2-2010182 |
Slice based RACH configuration or access barring |
Huawei, HiSilicon |
| R2-2010223 |
Discussion on slice aware overload control |
LG Electronics UK |
| 8.9.1 |
Organizational, Scope and Requirements |
|
| R2-2008716 |
LS on evaluation methodology for connected mode UE power saving enhancements (R1-2007419; contact: vivo, MediaTek) |
RAN1 |
| R2-2008719 |
LS on evaluation methodology for UE power saving enhancements (R1-2007425; contact: MediaTek) |
RAN1 |
| 8.9.2 |
Idle/inactive-mode UE power saving |
|
| R2-2008892 |
Power saving enhancements for paging reception |
Qualcomm Incorporated |
| R2-2008952 |
Discussion on paging enhancement |
Xiaomi Communications |
| R2-2009083 |
Paging enhancement in idle inactive mo de f or p owe r sa ving |
vivo |
| R2-2009092 |
Paging Enhancements to Reduce False Alarms |
Samsung Electronics Co., Ltd |
| R2-2009274 |
Paging enhancement using UE subgrouping |
Intel Corporation |
| R2-2009351 |
General requirements for potential paging enhancement |
Nokia, Nokia Shanghai Bell |
| R2-2009442 |
Paging enhancement for power saving |
LG Electronics Inc. |
| R2-2009464 |
Discussion on UE group based paging |
OPPO |
| R2-2009502 |
NR UE Power Save False Paging Mitigation |
Apple |
| R2-2009503 |
NR UE Power Save Wakeup and Paging Reception |
Apple |
| R2-2009504 |
NR UE Power Save UE Paging Grouping |
Apple |
| R2-2009642 |
Discussion on the UE grouping method |
ITRI |
| R2-2009784 |
Report of [Post111-e][907][ePowSav] UE grouping (Mediatek) |
MediaTek Inc. |
| R2-2009785 |
Paging Enhancements for UE Power Saving in NR |
MediaTek Inc. |
| R2-2009878 |
Consideration on Idle/inactive-mode UE power saving |
Lenovo, Motorola Mobility |
| R2-2009893 |
Discussion on reduction of unnecessary UE paging receptions |
Sony |
| R2-2009918 |
Potential TRS/CSI-RS occasion(s) |
Nokia, Nokia Shanghai Bell |
| R2-2009955 |
Paging enhancement to reduce unnecessary UE paging receptions |
Ericsson |
| R2-2010079 |
Paging Enhancements for UE Power Savings |
Convida Wireless |
| R2-2010244 |
Paging enhancements for idle/inactive-mode UE |
Huawei, HiSilicon, British Telecom |
| R2-2010245 |
On potential TRS/CSI-RS for idle/inactive-mode UE |
Huawei, HiSilicon |
| R2-2010397 |
UE Power profile based UE subgrouping |
CMCC |
| R2-2010629 |
Further consideration on the UE grouping methods |
ZTE corporation, Sanechips |
| R2-2010884 |
LS on Paging Enhancement |
RAN2 |
| R2-2010994 |
Power saving enhancements for paging reception |
Qualcomm Incorporated |
| 8.9.3 |
Other aspects, RAN2 impacts |
|
| R2-2008946 |
Discussion on TRS CSI-RS for RRC-IDLE and RRC-INACTIVE State UE |
Xiaomi Communications |
| R2-2009084 |
RAN2 impact on RLM/BFD relaxation for power saving |
vivo |
| R2-2009093 |
Other Enhancements for UE power saving |
Samsung Electronics Co., Ltd |
| R2-2009465 |
Potential RAN2 impacts for TRS/CSI-RS configuration |
OPPO |
| R2-2009956 |
Exposure of connected mode TRS occasions to Idle and Inactive mode |
Ericsson |
| 8.10.1 |
Organizational |
|
| R2-2008730 |
Reply LS on SA WG2 assumptions from conclusion of study on architecture aspects for using satellite access in 5G (R3-205795;; contact: Qualcomm) |
RAN3 |
| R2-2008884 |
NR-NTN: Positioning Methods |
Fraunhofer IIS, Fraunhofer HHI |
| R2-2009136 |
NR-NTN: TP for TS 38.300 |
Thales, Huawei, CATT, ZTE |
| R2-2009377 |
Discussion on CT1 LS on NAS procedure guard timers for GEO satellite |
OPPO |
| R2-2009378 |
Draft reply LS on NAS procedure guard timers for GEO satellite |
OPPO |
| R2-2009695 |
NR_NTN_solutions work plan |
THALES |
| R2-2010686 |
LS on NAS procedure guard timers for GEO satellite (C1-205967; contact: OPPO) |
CT1 |
| R2-2010696 |
Reply LS on SA WG2 assumptions from conclusion of study on architecture aspects for using satellite access in 5G (S2-2008307; contact: Intel) |
SA2 |
| R2-2010697 |
LS on signalling of satellite backhaul connection (S2-2008308; contact: Samsung) |
SA2 |
| R2-2010763 |
Draft reply LS on NAS procedure guard timers for GEO satellite |
OPPO |
| R2-2010781 |
NR-NTN: TP for TS 38.300 |
Thales, Huawei, CATT, ZTE |
| R2-2010793 |
Summary of offline 116 - NTN - Possible content of a reply LS to RAN3 |
Qualcomm |
| R2-2011041 |
Reply LS on SA WG2 assumptions from conclusion of study on architecture aspects for using satellite access in 5G (R3-207062; contact: Qualcomm) |
RAN3 |
| R2-2011230 |
Reply LS on NAS procedure guard timers for GEO satellite |
RAN2 |
| 8.10.2.1 |
RACH aspects |
|
| R2-2008911 |
RACH Aspects for an NTN- Observations and Proposals |
Samsung Research America |
| R2-2008936 |
Discussion on DRX operation associated with blind retransmission |
PANASONIC R&D Center Germany |
| R2-2008979 |
MAC issues for NTN |
Intel Corporation |
| R2-2008980 |
Timing advance for NTN |
Intel Corporation |
| R2-2008998 |
Consideration on TA compensation for HAPS and ATG case |
Beijing Xiaomi Mobile Software |
| R2-2009063 |
Enhancements for NTN on MAC Layer |
Nomor Research GmbH, Thales |
| R2-2009107 |
Discussion on RACH in NTN |
OPPO |
| R2-2009139 |
Discussion on Random Access |
Spreadtrum Communications |
| R2-2009451 |
Random Access procedure with timing reference at gateway vs satellite |
Qualcomm Inc |
| R2-2009514 |
On preamble ambiguity in NTN networks |
Apple |
| R2-2009595 |
Discussion on HARQ and RACH aspects in NTN |
Asia Pacific Telecom co. Ltd |
| R2-2009635 |
Consideration on MAC enhancements for NTN |
Huawei, HiSilicon |
| R2-2009636 |
Consideration on varying RTD for earth fixed beam case |
Huawei, HiSilicon |
| R2-2009860 |
Considerations on timing advance pre-compensation in NTN |
Lenovo, Motorola Mobility |
| R2-2009861 |
Preamble ambiguity for UE without TA pre-compensation capability |
Lenovo, Motorola Mobility |
| R2-2009932 |
Considerations on RACH procedure enhancements in NTN |
CAICT |
| R2-2009975 |
Support of UEs with/without UE-specific pre-compensation |
NEC Telecom MODUS Ltd. |
| R2-2009981 |
Discussion on 2-step RACH adaptation in NTN |
Nokia, Nokia Shanghai Bell |
| R2-2009984 |
NTN timers and common delay update in moving satellite scenario |
Nokia, Nokia Shanghai Bell |
| R2-2010091 |
Timing Advance management in NTN |
ETRI |
| R2-2010169 |
On Random Access in NTN |
Ericsson |
| R2-2010319 |
Considerations on Random Access in NTN |
ZTE Corporation, Sanechips |
| R2-2010339 |
Enhancement on random access procedure |
LG Electronics Inc. |
| R2-2010393 |
Discussion on pre-compensation in NTN |
CMCC |
| R2-2010451 |
Delay calculation and compensation in NTN |
InterDigital |
| R2-2010455 |
Summary of [Post111-e][908][NTN] RACH and HARQ feedback aspects |
InterDigital |
| R2-2010456 |
[DRAFT] LS to RAN1 on RAN2 agreements for ra-ResponseWindow and msgB-ResponseWindow |
InterDigital |
| R2-2010457 |
[DRAFT] LS to RAN1 on RAN2 agreements for enabling/disabling HARQ UL retransmission |
InterDigital |
| R2-2010664 |
Considerations on scheduling request in NTN |
CAICT |
| R2-2010764 |
Summary of offline 103 - NTN RACH and HARQ feedback aspects |
InterDigital |
| R2-2010980 |
On Random Access in NTN |
Ericsson |
| 8.10.2.2 |
Other MAC aspects |
|
| R2-2008836 |
Discussion on Other MAC aspects enhancements in NR NTN |
CATT |
| R2-2008912 |
MAC Aspects for an NTN- Observations and Proposals |
Samsung Research America |
| R2-2008969 |
Round trip delay offset for configured grant timers |
MediaTek Inc. |
| R2-2008970 |
LCP impact of disabling HARQ uplink retransmission |
MediaTek Inc. |
| R2-2008997 |
Consideration on HARQ blind retransmission |
Beijing Xiaomi Mobile Software |
| R2-2009064 |
Enhancements on UL scheduling for NTN |
Nomor Research GmbH, Thales |
| R2-2009108 |
HARQ impact on MAC procedures in NTN |
OPPO |
| R2-2009109 |
Discussion on other MAC issues in NTN |
OPPO |
| R2-2009140 |
Discussion on HARQ and related timers |
Spreadtrum Communications |
| R2-2009452 |
UL HARQ process without HARQ retransmission |
Qualcomm Inc |
| R2-2009511 |
On user plane latency reduction mechanisms in NTN networks |
Apple |
| R2-2009864 |
Discussion on DRX for NTN |
Lenovo, Motorola Mobility |
| R2-2009895 |
Other MAC aspects in NTN |
Sony |
| R2-2009987 |
Discussion on HARQ and UL scheduling enhancement aspects in NTN |
Nokia, Nokia Shanghai Bell |
| R2-2010168 |
On scheduling, HARQ, and DRX for NTN |
Ericsson |
| R2-2010320 |
Considerations on HARQ in NTN |
ZTE Corporation, Sanechips |
| R2-2010334 |
Discussion on disabling HARQ feedback and uplink retransmission |
LG Electronics Inc. |
| R2-2010335 |
Discussion on scheduling enhancement |
LG Electronics Inc. |
| R2-2010368 |
Further discussion of HARQ operation for NTN |
CMCC |
| R2-2010369 |
HARQ enhancement for NTN system |
CMCC |
| R2-2010533 |
HARQ aspects in NTN |
ETRI |
| 8.10.2.3 |
RLC and PDCP aspects |
|
| R2-2008896 |
[POST111e][909][NTN] Email Discussions Summary on RLC and PDCP aspects (MediaTek) |
MediaTek Inc. |
| R2-2008913 |
RLC and PDCP Aspects for an NTN- Observations and Proposals |
Samsung Research America |
| R2-2009070 |
Remaining Aspects on Enhancements for NTN on RLC and PDCP Timers |
Nomor Research GmbH, Thales |
| R2-2009647 |
Consideration of RLC and PDCP in NTN |
China Telecom |
| R2-2010167 |
On RLC and PDCP for NTN |
Ericsson |
| R2-2010170 |
Additional RLC and PDCP aspects for NTN |
Sequans Communications |
| 8.10.3.1 |
Earth fixed/moving beams related issues |
|
| R2-2008838 |
Discussion on tracking area for earth moving cells |
CATT |
| R2-2008914 |
Beam Aspects for an NTN- Observations and Proposals |
Samsung Research America |
| R2-2009110 |
Discussion on earth fixed and moving cells |
OPPO |
| R2-2009141 |
Discussion on Floor Layout Information |
Spreadtrum Communications |
| R2-2009256 |
Earth fixed/moving beams related issues |
THALES |
| R2-2009453 |
Gateway switch procedure for earth fixed and moving beam scenario |
Qualcomm Inc |
| R2-2009512 |
Analysis of mobility management solutions with earth fixed and earth moving beams/cells in NTN networks |
Apple |
| R2-2009773 |
On Feeder Link Mobility in Transparent Satellite Payload Scenarios |
Nokia, Nokia Shanghai Bell |
| R2-2009805 |
Tracking area management for earth moving cells |
ZTE corporation, Sanechips |
| R2-2009820 |
[POST111e][910][NTN] Impacts of earth fixed and moving beams (Ericsson) |
Ericsson |
| R2-2009823 |
Aspects for Earth fixed and Earth moving beams for NTN |
Ericsson |
| R2-2009977 |
Mobility scenarios of Earth fixed/moving beams |
NEC Telecom MODUS Ltd. |
| R2-2009980 |
TAI update for earth moving cell |
NEC Telecom MODUS Ltd. |
| R2-2010261 |
Discussion on soft feeder link switch |
Huawei, HiSilicon |
| R2-2010377 |
Considerations on Soft TAI Update |
CMCC |
| R2-2010447 |
Discussion on service link/feeder link switch in NTN |
Xiaomi Communications |
| R2-2010452 |
Feeder-link switch |
InterDigital |
| R2-2010480 |
Tracking area management for earth moving cells |
ZTE corporation, Sanechips |
| R2-2010765 |
Summary of offline 104 - Misc CP issues |
Ericsson |
| R2-2010766 |
Draft LS to RAN1 on same PCI during service link switch |
Ericsson |
| 8.10.3.2 |
Idle/Inactive mode |
|
| R2-2008814 |
Consideration on idle mode issues in NTN |
CAICT |
| R2-2008837 |
Remaining Issues of IDLE and Inactive Mode for NTN |
CATT |
| R2-2008897 |
On Cell Re-selection in NR-NTN |
MediaTek Inc. |
| R2-2008898 |
Improving Tracking Area Updates in NR-NTN |
MediaTek Inc. |
| R2-2008915 |
Idle and Inactive Mode Aspects for an NTN- Observations and Proposals |
Samsung Research America |
| R2-2008984 |
Idle mode operation in NTN |
Intel Corporation |
| R2-2009111 |
Discussion on idle/inactive mode procedures in NTN |
OPPO |
| R2-2009120 |
Fixed Tracking Area and the Tracking Area Code in NTN |
PANASONIC R&D Center Germany |
| R2-2009142 |
Discussion on Mobility |
Spreadtrum Communications |
| R2-2009255 |
Idle mode procedures in NR NTN |
THALES |
| R2-2009454 |
Cell selection and reselection enhancements |
Qualcomm Inc |
| R2-2009510 |
Cell Selection and Reselection solutions for NTN networks |
Apple |
| R2-2009597 |
Control Plane for Idle mode UE |
Xiaomi |
| R2-2009621 |
Enhancements on cell reselection |
Xiaomi |
| R2-2009637 |
Discussion on RRC_IDLE mode issues in NTN |
Huawei, HiSilicon |
| R2-2009645 |
Ephemeris data to be included in system information |
ITRI |
| R2-2009648 |
The consideration of satellite ephemeris in NTN |
China Telecom |
| R2-2009774 |
IDLE mode aspects for Non-Terrestrial Networks (NTN) |
Nokia, Nokia Shanghai Bell |
| R2-2009818 |
Idle mode aspects for NTN |
Ericsson LM |
| R2-2009862 |
Ephemeris data provision in NTN |
Lenovo, Motorola Mobility |
| R2-2009894 |
Idle mode aspects in NTN |
Sony |
| R2-2010094 |
Earth moving beam scenarios in Earth fixed tracking areas |
ETRI |
| R2-2010260 |
Considerations on satellite ephemeris |
Huawei, HiSilicon |
| R2-2010370 |
Discussion of UE location information assistant for cell selection and reselection in NTN |
CMCC |
| R2-2010453 |
Satellite ephemeris in NTN |
InterDigital |
| R2-2010578 |
Idle mode issues in NR NTN |
LG Electronics Inc. |
| 8.10.3.3 |
Connected mode |
|
| R2-2008833 |
Feeder Link Switch |
CATT |
| R2-2008834 |
Open Issues for Measurements in NTN |
CATT |
| R2-2008835 |
Discussion on UE-based location requirement in NR NTN |
CATT |
| R2-2008916 |
Connected Mode Aspects for an NTN- Observations and Proposals |
Samsung Research America |
| R2-2008973 |
Service continuity between NTN and TN |
HUGHES Network Systems Ltd, Thales, BT, Turkcell, Vodafone |
| R2-2008981 |
Feeder link switch over for NTN |
Intel Corporation |
| R2-2008982 |
Mobility enhancement for NTN |
Intel Corporation |
| R2-2009112 |
Discussion on mobility management for connected mode UE in NTN |
OPPO |
| R2-2009121 |
Overhead Reduction for the Handover Procedure in NTN |
PANASONIC R&D Center Germany |
| R2-2009443 |
Measurement window enhancements |
LG Electronics Inc. |
| R2-2009455 |
Configuration and triggering of CHO |
Qualcomm Inc |
| R2-2009456 |
SMTC and measurement gap configuration |
Qualcomm Inc |
| R2-2009513 |
Analysis of proposed conditional handover solutions for NTN Networks |
Apple |
| R2-2009772 |
Simulation assumptions for evaluating NTN mobility |
Nokia, Nokia Shanghai Bell |
| R2-2009803 |
Report of [Post111-e] [911] [NTN] Connected mode aspects (ZTE) |
ZTE corporation, Sanechips |
| R2-2009804 |
Consideration on the measurement configuration and reporting in NTN |
ZTE corporation, Sanechips |
| R2-2009821 |
Connected mode aspects for NTN |
Ericsson |
| R2-2009859 |
Conditional handover in NTN |
Lenovo, Motorola Mobility |
| R2-2009863 |
Considerations on measurements in NTN |
Lenovo, Motorola Mobility |
| R2-2009896 |
Mobility management in NTN |
Sony |
| R2-2010262 |
Discussion on enhancements for connected mode in NTN |
Huawei, HiSilicon |
| R2-2010371 |
Discussion of mobility enhancements for NTN |
CMCC |
| R2-2010446 |
Discussion on mobility management in NTN |
Xiaomi Communications |
| R2-2010454 |
Connected mode mobility in NTN |
InterDigital |
| R2-2010478 |
Report of [Post111-e] [911] [NTN] Connected mode aspects (ZTE) |
ZTE corporation, Sanechips |
| R2-2010479 |
Consideration on the measurement configuration and reporting in NTN |
ZTE corporation, Sanechips |
| R2-2010579 |
New triggering condition for CHO in NTN |
LG Electronics Inc. |
| R2-2010767 |
Summary of offline 105 - RRC aspects |
ZTE Corporation |
| R2-2010768 |
Summary of offline 106 - SMTC and gaps |
CATT |
| R2-2010794 |
Summary of offline 105 - RRC aspects - second round |
ZTE Corporation |
| R2-2010795 |
Summary of offline 106 - SMTC and gaps - second round |
CATT |
| 8.11.1 |
Organizational |
|
| R2-2008707 |
LS on Latency of NR Positioning Protocols (R1-2007264; contact: Intel) |
RAN1 |
| R2-2008766 |
LS on Requirements on positioning for UAS (S6-200269; contact: InterDigital) |
SA6 |
| R2-2010576 |
draft LS to capture TP for TR 38.857 |
Ericsson |
| R2-2010577 |
TP for TR 38.857 Study on NR Positioning |
Ericsson, Swift Navigation |
| 8.11.2 |
Enhancements for commercial use cases |
|
| R2-2008775 |
Discussion on on-demand DL-PRS |
OPPO |
| R2-2008776 |
Positioning in RRC_IDLE and RRC_INACTIVE state |
OPPO |
| R2-2008810 |
Further discussion on ehancements for commercial use cases |
CATT |
| R2-2008885 |
Discussion on Positioning in Idle/Inactive mode |
InterDigital, Inc. |
| R2-2008886 |
Discussion on End-to-End Latency Reduction for DL/UL Positioning |
InterDigital, Inc. |
| R2-2008887 |
Discussion on On Demand Reference Signals for Positioning |
InterDigital, Inc. |
| R2-2009001 |
Report of [Post111-e][625][POS] End-to-end latency analysis (Intel) |
Intel Corporation |
| R2-2009002 |
Support of positioning in idle/inactive mode |
Intel Corporation |
| R2-2009023 |
Solution directions to reduce end-to-end latency |
Intel Corporation |
| R2-2009039 |
Discussion on positioning enhancement |
vivo Mobile Communication Co., |
| R2-2009040 |
Procedure of on-demand PRS |
vivo Mobile Communication Co., |
| R2-2009041 |
Positioning in RRC idle and inactive state |
vivo Mobile Communication Co., |
| R2-2009137 |
Discussion on positioning enhancements for commercial use cases |
Spreadtrum Communications |
| R2-2009286 |
Reporting movement models |
Fraunhofer IIS |
| R2-2009287 |
Reporting the situational quality of RAT and RAT-independent technologies |
Fraunhofer IIS, Fraunhofer HHI |
| R2-2009574 |
Discussion on PRS enhancements |
Beijing Xiaomi Electronics |
| R2-2009577 |
Positioning enhancements on RRC idle/inactive UE and latency reduction |
Beijing Xiaomi Electronics |
| R2-2009897 |
Considerations on potential positioning enhancements |
Sony |
| R2-2010072 |
Enhancements for commercial use cases |
Ericsson |
| R2-2010095 |
NR Positioning Enhancements |
Qualcomm Incorporated |
| R2-2010096 |
NR Positioning Latency Analysis and Enhancements |
Qualcomm Incorporated |
| R2-2010097 |
On-Demand PRS |
Qualcomm Incorporated |
| R2-2010131 |
Reporting movement models |
Fraunhofer IIS, Fraunhofer HHI |
| R2-2010161 |
On-demand PRS transmission and dynamic PRS resource allocation |
Nokia, Nokia Shanghai Bell |
| R2-2010276 |
Discussion on IDLE INACTIVE pos, on-demand PRS and latency analysis |
Huawei, HiSilicon |
| R2-2010277 |
Discussion on R17 positioning enhancement |
Huawei, HiSilicon |
| R2-2010472 |
Disucssion on IDLE/INACTIVE mode positioning |
ZTE Corporation, Sanechips |
| R2-2010473 |
Discussion on on-demand PRS |
ZTE Corporation, Sanechips |
| R2-2010627 |
Discussion on enhancement for commercial use cases |
Samsung R&D Institute UK |
| R2-2010648 |
Support for positioning in idle/inactive mode |
Samsung R&D Institute UK |
| R2-2010669 |
Summary of 8.11.2 Enhancements for commercial use cases |
CATT |
| R2-2010866 |
Summary of latency results |
Intel Corporation |
| R2-2010867 |
Draft Reply LS on Latency of NR Positioning Protocols |
Intel |
| R2-2010868 |
Gathering of latency enhancement solutions (CATT)? |
CATT |
| R2-2010872 |
Summary of latency results |
Intel Corporation |
| R2-2010873 |
Reply LS on Latency of NR Positioning Protocols |
RAN2 |
| R2-2010881 |
TP on the proposed latency enhancements for TR 38.857 |
CATT |
| 8.11.3.1 |
KPIs and use cases |
|
| R2-2008811 |
Discussion on integrity service level |
CATT |
| R2-2009129 |
Summary of [Post111-e][626][POS] Email Discussion on integrity use cases and specification impacts |
Swift Navigation |
| R2-2009760 |
Positioning integrity for Industrial IoT use cases |
Nokia, Nokia Shanghai Bell |
| R2-2009898 |
Discussion on Integrity of positioning information |
Sony |
| R2-2010074 |
Industrial IoT use-case |
Ericsson |
| R2-2010090 |
Integrity and reliability for IIoT positioning use cases |
Convida Wireless |
| R2-2010098 |
Discussion on including PL Availability as an additional integrity KPI |
ESA |
| R2-2010475 |
Discussion on integrity&error source factor transmission |
ZTE Corporation, Sanechips |
| R2-2010877 |
TP on Integrity KPIs, Concepts, Use Cases |
Swift Navigation |
| R2-2010878 |
TP on Integrity Error Sources |
Swift Navigation |
| R2-2010879 |
TP on Integrity Methodologies |
Swift Navigation |
| R2-2010880 |
Email Summary [AT112-e][614][POS] GNSS Integrity |
Swift Navigation |
| 8.11.3.2 |
Error sources, threat models, occurrence rates and failure modes |
|
| R2-2008812 |
Discussion on error sources, threat models, occurrence rates and failure modes |
CATT |
| R2-2009282 |
Error sources, threat models, occurrence rates and failure modes |
Fraunhofer IIS |
| R2-2009331 |
Discussion on GNSS Integrity Errors |
Swift Navigation, Ericsson, Intel Corporation, u-blox |
| R2-2010061 |
Text Proposal on GNSS position integrity error sources |
ESA |
| R2-2010073 |
GNSS position integrity error sources |
Ericsson |
| R2-2010135 |
Error sources, threat models, occurrence rates and failure modes |
Fraunhofer IIS, Fraunhofer HHI |
| R2-2010278 |
Discussion on threat models and failure modes |
Huawei, HiSilicon |
| R2-2010642 |
Introduction of Integrity monitoring for GNSS and its error |
Samsung R&D Institute UK |
| R2-2010700 |
Summary of 8.11.3.2 Error sources threat models occurrence rates and failure modes |
Intel Corporation |
| 8.11.3.3 |
Methodologies for network-assisted and UE-assisted integrity |
|
| R2-2008774 |
Discussion on methodology for integrity |
OPPO |
| R2-2008813 |
Discussion on methodologies for network-assisted and UE-assisted integrity |
CATT |
| R2-2008888 |
Discussion on methodologies for network-assisted and UE-assisted integrity |
InterDigital, Inc. |
| R2-2009003 |
Methodologies for network-assisted and UE-assisted integrity |
Intel Corporation, Swift Navigation |
| R2-2009043 |
Integrity signaling and procedures |
vivo Mobile Communication Co., |
| R2-2009138 |
Discussion on integrity methodologies for network-assisted and UE-assisted integrity |
Spreadtrum Communications |
| R2-2009333 |
TP for GNSS Integrity Methodologies |
Swift Navigation, Ericsson, Intel Corporation, u-blox |
| R2-2009530 |
Discussion on Positioning Integrity |
Apple |
| R2-2009578 |
Discussion on methodologies for positioning integrity |
Beijing Xiaomi Electronics |
| R2-2009761 |
Signalling for Positioning Integrity Support |
Nokia, Nokia Shanghai Bell |
| R2-2010075 |
Methodologies for network-assisted and UE-assisted integrity |
Ericsson |
| R2-2010279 |
Discussion for network-assisted and UE-assisted integrity |
Huawei, HiSilicon |
| R2-2010474 |
Discussion of the methodologies for network-assisted and UE-assisted integrity |
ZTE Corporation, Sanechips |
| R2-2010675 |
Summary of 8.11.3.3: Methodologies for network-assisted and UE-assisted integrity |
InterDigital, Inc. |
| 8.12.1 |
Organizational |
|
| R2-2009615 |
Way forward for RedCap in RAN2 |
Ericsson |
| R2-2009616 |
TR38875 update |
Ericsson |
| R2-2009617 |
Summary of [Post111-e][912][RedCap] TP for TR |
Ericsson |
| R2-2010784 |
TP for TR38875 |
Ericsson |
| R2-2011165 |
TP for TR38875 |
Ericsson |
| 8.12.2 |
Framework for reduced capabilities |
|
| R2-2008951 |
General views on Higher-layer impacts for Redcap devices |
Xiaomi Communications |
| 8.12.2.1 |
Principles for how to define and constrain reduced capabilities |
|
| R2-2008889 |
Define and constrain RedCap UEs |
Qualcomm Incorporated |
| R2-2009004 |
Report of [POST111e][913][REDCAP] Definition and constraining of reduced capabilities (Intel) |
Intel Corporation |
| R2-2009008 |
Device type definition and how to signal the device type to network |
Fujitsu |
| R2-2009085 |
UE type defination and constraining for RedCap UEs |
vivo, Guangdong Genius |
| R2-2009104 |
Discussion on definition of reduced capabilities |
OPPO |
| R2-2009115 |
On the definition of a RedCap device type |
MediaTek Inc. |
| R2-2009248 |
Consideration on definition and constraining of Reduced Capability |
ZTE Corporation, Sanechips |
| R2-2009361 |
On Definition and Constraint of Reduced Capabilities |
CATT |
| R2-2009618 |
Framework and principles for RedCap |
Ericsson |
| R2-2009762 |
Discussion on how to define and constrain the REDCAP UE |
China Telecommunications |
| R2-2009933 |
Capability framework and constraining of RedCap UE |
Huawei, HiSilicon |
| R2-2009957 |
Discussion on how to ensure devices only access to intended services |
China Telecommunications |
| R2-2009958 |
Discussion on how to ensure devices only access to intended services |
China Telecommunications |
| R2-2010225 |
Discussion on the intended use cases for RedCap UEs |
LG Electronics UK |
| R2-2010376 |
Discussion on the definition and constraining of reduced capabilities |
CMCC |
| R2-2010458 |
Reduced capability device type definition |
InterDigital |
| R2-2010785 |
Summary of offline 112 - RedCap capabilities |
Intel Corporation |
| 8.12.2.2 |
Identification and access restrictions |
|
| R2-2008890 |
Impact of reduced capabilities on idle mode procedures |
Qualcomm Incorporated |
| R2-2008947 |
Discussion on Identification and UE access restrictions for Redcap devices |
Xiaomi Communications |
| R2-2008996 |
Early identification of RedCap UEs |
Samsung |
| R2-2009009 |
Access restriction of RedCap UE |
Fujitsu |
| R2-2009010 |
UAC for RedCap UE |
Intel Corporation, Facebook |
| R2-2009086 |
Identification and access restrictions for RedCap UEs |
vivo, Guangdong Genius |
| R2-2009105 |
Discussion on RedCap UE’s access control |
OPPO |
| R2-2009249 |
Further consideration on Identification and access restrictions |
ZTE Corporation, Sanechips |
| R2-2009362 |
On Identification and Access Restrictions for Reduced Capabilities UE |
CATT |
| R2-2009515 |
Ineffectiveness of MSG3 based RAN node identification of RedCap UE |
Apple |
| R2-2009619 |
Identification and access control of RedCap Ues |
Ericsson |
| R2-2009670 |
Early identification of Redcap UEs |
Lenovo, Motorola Mobility |
| R2-2009751 |
Discussion on identification and access restriction of REDCAP UE |
China Telecommunications |
| R2-2009800 |
Cell access for REDCAP UE with reduced bandwidth |
Nokia, Nokia Shanghai Bell |
| R2-2009817 |
RedCap UE identification options |
NEC |
| R2-2009871 |
Cell restriction and UAC enhancement for REDCAP Ues |
Lenovo, Motorola Mobility |
| R2-2009916 |
Cell access restrictions for REDCAP UE |
Nokia, Nokia Shanghai Bell |
| R2-2009934 |
Identification and access restriction of RedCap UE |
Huawei, HiSilicon |
| R2-2009936 |
Summary of email discussion 914 on UE identification and access restrictions |
Huawei |
| R2-2010224 |
Consideration on access restriction during Msg3 |
LG Electronics UK |
| R2-2010786 |
Summary of offline 113 - RedCap identification and access restrictions |
Huawei |
| 8.12.3 |
UE power saving and battery lifetime enhancement |
|
| R2-2008891 |
DRX enhancements for RedCap UEs |
Qualcomm Incorporated |
| R2-2008948 |
Discussion on e-DRX for Redcap Devices |
Beijing Xiaomi Mobile Software |
| R2-2009011 |
Support of extend paging DRX cycle for Inactive UE |
Intel Corporation |
| R2-2009022 |
Relax measurement for stationary and low mobility devices |
Intel Corporation |
| R2-2009087 |
RRM relaxation for power saving |
vivo, Guangdong Genius |
| R2-2009106 |
Discussion on RRM relaxation |
OPPO |
| R2-2009116 |
Further considerations for eDRX |
MediaTek Inc. |
| R2-2009247 |
Discussion on eDRX for Redcap UE |
ZTE Corporation, Sanechips |
| R2-2009363 |
On eDRX for NR RRC Inactive and Idle |
CATT |
| R2-2009364 |
Summary of email discussion 915 - UE power saving features |
CATT |
| R2-2009532 |
Support of 2.56 eDRX cycle and emergency broadcast reception for RedCap UEs |
Apple, Facebook |
| R2-2009620 |
RedCap power saving enhancements |
Ericsson |
| R2-2009877 |
RRM relaxation for stationary UE with reduced capability |
Lenovo, Motorola Mobility |
| R2-2009917 |
Power saving and battery lifetime enhancement for REDCAP UE |
Nokia, Nokia Shanghai Bell |
| R2-2009935 |
eDRX and RRM measurement relaxation for RedCap UE |
Huawei, HiSilicon |
| R2-2010113 |
eDRX for Reduced Capability NR Devices |
Convida Wireless |
| R2-2010392 |
eDRX for reduced capability UE |
CMCC |
| R2-2010406 |
Introducing Extended DRX for RRC Inactive and/or Idle |
Samsung |
| R2-2010580 |
RRM relaxation for stationary RedCap Ues |
LG Electronics Inc. |
| R2-2010592 |
RRM relaxation for RedCap devices |
Samsung Electronics |
| R2-2010787 |
Summary of offline 114 - RedCap power saving |
CATT |
| R2-2011166 |
Summary of offline 114 - RedCap power saving- second round |
CATT |
| 8.13 |
SON/MDT |
|
| R2-2010085 |
Immediate MDT with MR-DC and Intermediate MDT for early measurements |
Samsung Telecommunications |
| R2-2010086 |
Logged MDT with MR-DC and related early measurments aspects |
Samsung Telecommunications |
| 8.13.1 |
Organizational |
|
| R2-2008723 |
LS to RAN2 on RACH report for SgNB (R3-205662; contact: CATT) |
RAN3 |
| R2-2008725 |
LS on Successful Handover Report (R3-205759; contact: Samsung) |
RAN3 |
| R2-2008731 |
LS to RAN2 on RACH report for 2-step RACH (R3-205797; contact: CATT) |
RAN3 |
| R2-2008763 |
Reply LS on limitation of Propagation of immediate MDT configuration in case of Xn inter-RAT HO (S5-204474; contact: Ericsson) |
SA5 |
| R2-2008842 |
[draft] Reply LS on UE RACH report for SgNBs |
CATT |
| R2-2008843 |
[draft] Reply LS on RACH report for 2-step RACH |
CATT |
| 8.13.2.1 |
Handover related SON aspects |
|
| R2-2008844 |
Discussion on CHO and DAPS Mobility Enhancement |
CATT |
| R2-2008999 |
CHO support for MDT/SON |
Intel Corporation |
| R2-2009017 |
Consideration on handover related SON |
OPPO |
| R2-2009396 |
SON aspects of DAPS HO and Fast MCG Recovery Optimizations |
QUALCOMM Incorporated |
| R2-2009424 |
SON for MRO |
Nokia, Nokia Shanghai Bell |
| R2-2009632 |
Discussion on RLF report in CHO and DAPS case |
SHARP Corporation |
| R2-2009682 |
Discussion on SON enhancements for Successful HO |
vivo |
| R2-2009683 |
Discussion on SON enhancements for DAPS HO |
vivo |
| R2-2009853 |
MRO Enhancement for Inter-RAT handover |
Lenovo, Motorola Mobility |
| R2-2009854 |
SON Enhancements for CHO |
Lenovo, Motorola Mobility |
| R2-2009855 |
MRO Enhancement for DAPS Handover |
Lenovo, Motorola Mobility |
| R2-2010146 |
CHO and DAPS-related SON aspects |
Ericsson |
| R2-2010174 |
Discussion on handover related SON aspects |
Huawei, HiSilicon |
| R2-2010321 |
Handover related SON aspects |
ZTE Corporation, Sanechips |
| R2-2010361 |
SON Enhancements related to HO |
Samsung |
| R2-2010394 |
SON Enhancement for CHO and DAPS |
CMCC |
| R2-2010509 |
Disucssion on rel-17 radio link failure report |
NTT DOCOMO, INC. |
| R2-2010995 |
Summary of AI 8.13.2.1 - Handover related SON aspects |
Ericsson |
| 8.13.2.2 |
2-step RA related SON aspects |
|
| R2-2008845 |
Discussion on RACH Report for 2-step RACH |
CATT |
| R2-2009019 |
Discussion on 2-step RACH reporting for SON |
OPPO |
| R2-2009061 |
Discussion on 2-step RA aspects of SON |
China Telecom Corporation Ltd. |
| R2-2009399 |
RA-report enhancements for 2-step RACH |
QUALCOMM Incorporated |
| R2-2009425 |
2-step RACH reporting |
Nokia, Nokia Shanghai Bell |
| R2-2009631 |
Discussion on RA information for 2-step RA |
SHARP Corporation |
| R2-2009684 |
Discussion on SON enhancements for 2-step RACH |
vivo |
| R2-2010147 |
2-Step RA information reported by the UE for SON purposes |
Ericsson |
| R2-2010175 |
Discussion on 2 step RA related SON aspects |
Huawei, HiSilicon |
| R2-2010322 |
Enhance UE reporting for 2stepRA |
ZTE Corporation, Sanechips |
| R2-2010362 |
SON Enhancements related to 2-step RA |
Samsung |
| R2-2010395 |
SON Enhancement for 2-step RA |
CMCC |
| R2-2011007 |
Summary of AI 8.13.2.2 - 2-step RA related SON aspects |
OPPO |
| 8.13.2.3 |
Other WID related SON features |
|
| R2-2008918 |
UE RACH Report for SN |
CATT |
| R2-2009018 |
Consideration on successful handover report and UE history information in EN-DC |
OPPO |
| R2-2009397 |
Successful Handover Report |
QUALCOMM Incorporated |
| R2-2009400 |
Enhancements to Mobility History Information |
QUALCOMM Incorporated |
| R2-2009426 |
Refined UL Coverage Outage Detection |
Nokia, Nokia Shanghai Bell |
| R2-2009685 |
Discussion on RACH report for SgNB |
vivo |
| R2-2009850 |
MRO Enhancement for fast MCG link recovery |
Lenovo, Motorola Mobility |
| R2-2010148 |
Other WID related SON features |
Ericsson |
| R2-2010176 |
Discussion on other SON aspects |
Huawei, HiSilicon |
| R2-2010323 |
Considerations on RAN3 concerned issues |
ZTE Corporation, Sanechips |
| R2-2010400 |
Enhancements related to successful HO report & MCGFailureInformation |
Samsung |
| R2-2010459 |
Discussion on successful handover report |
NTT DOCOMO, INC. |
| R2-2010508 |
Discussion on collection of UE history information in EN-DC |
NTT DOCOMO, INC. |
| R2-2010526 |
Discussion on conditional PSCell addition/change failure report |
NTT DOCOMO, INC. |
| R2-2010608 |
Discussion on rel-17 Radio Link Failure Report for CG failure aspects |
NTT DOCOMO INC. |
| R2-2010892 |
Report of email discussion of other WID related SON features |
Ericsson |
| R2-2010896 |
[Offline-803][NR/R17 SON/MDT] Information needed in UE report for CHO cases (Ericsson) |
Ericsson |
| R2-2010996 |
Summary of AI 8.13.2.3 - Other WID related SON features |
Ericsson |
| 8.13.3 |
MDT |
|
| R2-2009263 |
On the need for enhancements to the MDT framework |
Fraunhofer HHI, Fraunhofer IIS |
| R2-2010220 |
Summary on 8.13.3 MDT |
Huawei |
| R2-2010897 |
Report of [AT112-e][804][NR/R17 SON/MDT] MDT enhancements (Huawei) |
Huawei (Summary rapporteur) |
| 8.13.3.1 |
Immediate MDT enhancements |
|
| R2-2008846 |
Immediate MDT Enhancements for M6 |
CATT |
| R2-2009020 |
Enhancement of Immediate MDT in MR-DC |
OPPO |
| R2-2009395 |
On the configuration and accuracy of M5, M6, and M7 measurements in split-bearer |
QUALCOMM Incorporated |
| R2-2009427 |
Immediate MDT enhancements |
Nokia, Nokia Shanghai Bell |
| R2-2009687 |
Discussion on immediate MDT enhancements |
vivo |
| R2-2010034 |
On Immediate MDT Enhancements |
Ericsson |
| R2-2010177 |
Discussion on immediate MDT enhancements |
Huawei, HiSilicon |
| R2-2010324 |
Immediate MDT enhancements |
ZTE Corporation, Sanechips |
| R2-2010698 |
Summary on 8.13.3.1 Immediate MDT enhancements |
Huawei |
| R2-2011011 |
Summary on 8.13.3.1 Immediate MDT enhancements |
Huawei |
| 8.13.3.2 |
Logged MDT enhancements |
|
| R2-2008847 |
Logged MDT in DC Scenario |
CATT |
| R2-2009016 |
Consideration of logged MDT enhancements |
OPPO |
| R2-2009391 |
Logged measurement Enhancements |
QUALCOMM Incorporated |
| R2-2009434 |
Enhancements for Logged MDT and RLFreporting |
Nokia, Nokia Shanghai Bell |
| R2-2009686 |
Discussion on logged MDT enhancements |
vivo |
| R2-2010035 |
On logged MDT related enhancements |
Ericsson |
| R2-2010178 |
Discussion on logged MDT enhancements |
Huawei, HiSilicon |
| R2-2010325 |
Logged MDT enhancements |
ZTE Corporation, Sanechips |
| R2-2010396 |
MDT enhancement for on-demand SI |
CMCC |
| R2-2010401 |
MDT Enhancements |
Samsung |
| R2-2010462 |
Discussion on erroneous connection release |
Xiaomi communications |
| R2-2010699 |
Summary on 8.13.3.2 Logged MDT enhancements |
Huawei |
| R2-2011012 |
Summary on 8.13.3.2 Logged MDT enhancements |
Huawei |
| 8.13.4 |
L2 Measurements |
|
| R2-2009021 |
L2 measurement for split bearers |
OPPO |
| R2-2009435 |
Need for L2 measurements enhancements |
Nokia, Nokia Shanghai Bell |
| R2-2010045 |
On additional layer-2 measurements |
Ericsson |
| R2-2010179 |
Discussion on L2M |
Huawei, HiSilicon |
| R2-2010326 |
Consideration on L2 measurement enhancement |
ZTE Corporation, Sanechips |
| R2-2010985 |
Summary for AI_8.13.4 L2 Measurements |
vivo |
| 8.14 |
NR QoE SI |
|
| R2-2008724 |
New service type of NR QoE (R3-205724; contact: ZTE) |
RAN3 |
| R2-2008728 |
LS on Transport of NR QoE Reports in the RAN (R3-205785; contact: Ericsson) |
RAN3 |
| R2-2009436 |
QoE Measurement Collection in NR |
Nokia, Nokia Shanghai Bell |
| R2-2009594 |
Introduce the VR and MBMS service for NR QoE |
China Unicom |
| R2-2010004 |
Mobility Support for NR QoE Management |
Ericsson |
| R2-2010180 |
Discussion on NR QoE |
Huawei, HiSilicon |
| R2-2010476 |
Discussion on QoE in NR |
ZTE Corporation, Sanechips |
| R2-2010594 |
NR QoE management |
Samsung Electronics |
| R2-2011158 |
Handling of RAN3 LS on QoE Measurement Collection |
Ericsson |
| R2-2011159 |
Reply LS on Transport of NR QoE Reports in the RAN |
Ericsson |
| 8.15.1 |
Organizational |
|
| R2-2008761 |
LS on new PQI support for PC5 communication (S2-2006588; contact: Oppo) |
SA2 |
| R2-2008767 |
Reply LS to extend the scope of eV2X (SP-191379; contact: Telecom Italia) |
SA |
| R2-2008944 |
RAN2 Work Plan for Release-17 NR Sidelink enhancements |
LG Electronics France |
| R2-2010672 |
LS on PC5 DRX operation (S2-2008326; contact: LGE) |
SA2 |
| R2-2011121 |
Reply LS on new PQI support for PC5 communication (R1-2009621; contact: OPPO) |
RAN1 |
| 8.15.2 |
SL DRX for broadcast groupcast and unicast |
|
| R2-2008772 |
Discussion on DRX for sidelink |
OPPO |
| R2-2008850 |
Discussion on Sidelink DRX |
CATT |
| R2-2008943 |
Discussion on Sidelink DRX |
LG Electronics France |
| R2-2008971 |
Methods for configuring SL DRX and Paging |
Sierra Wireless, S.A. |
| R2-2008978 |
On general sidelink DRX design |
Intel Corporation |
| R2-2008988 |
Alignment of DRX wake up times |
Intel Corporation |
| R2-2009025 |
draft LS to RAN1 on SL DRX |
ZTE Corporation, Sanechips |
| R2-2009026 |
Discussion on Sidelink DRX |
ZTE Corporation, Sanechips |
| R2-2009133 |
Sidelink DRX for Power Saving |
Fujitsu |
| R2-2009210 |
Initial Discussion on SL DRX |
InterDigital |
| R2-2009211 |
Discussion on Uu DRX for SL UE |
InterDigital |
| R2-2009231 |
DRX for sidelink communications |
Ericsson |
| R2-2009232 |
Interaction between partial sensing and DRX |
Ericsson |
| R2-2009289 |
Considerations for SL DRX |
Samsung Research America |
| R2-2009413 |
Consideration on the sidelink DRX for unicast, groupcast and broadcast |
Huawei, HiSilicon |
| R2-2009527 |
Discussion on Sidelink DRX |
Apple |
| R2-2009696 |
Discontinuous reception and transmission in SL |
Lenovo, Motorola Mobility |
| R2-2009833 |
SL DRX for broadcast groupcast and unicast |
vivo |
| R2-2009899 |
Discussion on Introduction of Sidelink DRX |
Sony |
| R2-2009923 |
Discussion on Sidelink DRX |
Qualcomm Finland RFFE Oy |
| R2-2009993 |
NR SL DRX |
Fraunhofer IIS, Fraunhofer HHI |
| R2-2010058 |
On configuration and operation of SL DRX |
Nokia, Nokia Shanghai Bell |
| R2-2010140 |
Sidelink DRX Considerations |
Convida Wireless |
| R2-2010142 |
Sidelink and Uu DRX |
Convida Wireless |
| R2-2010332 |
On SL DRX |
MediaTek Inc. |
| R2-2010433 |
Discussion on Sidelink DRX |
ASUSTeK |
| R2-2010468 |
Discussion on sidelink DRX timer handling |
Xiaomi communications |
| R2-2010961 |
LS to RAN1 on SL DRX design |
RAN2 |
| 8.15.3 |
Resource allocation enhancements RAN2 scope |
|
| R2-2008773 |
Discussion on Inter-UE Coordination for sidelink |
OPPO |
| R2-2008851 |
Consideration on Resource Allocation Enhancements |
CATT |
| R2-2008986 |
Resource Allocation Enhancements for NR Sidelink |
Intel Corporation |
| R2-2009027 |
resource allocation to reduce power consumption |
ZTE Corporation, Sanechips |
| R2-2009028 |
Discussion on sidelink inter-UE coordination |
ZTE Corporation, Sanechips |
| R2-2009134 |
Dual-mode Configuration and Selection Mechanism for NR Sidelink |
Fujitsu |
| R2-2009212 |
RAN2 Aspects of Resource Allocation with Inter-UE Coordination |
InterDigital |
| R2-2009290 |
Enhanced resource allocation |
Samsung Research America |
| R2-2009411 |
Consideration on resource allocation enhancement in Rel-17 NR SL enhancement |
Huawei, HiSilicon |
| R2-2009528 |
Discussion on Resource Allocation for Pedestrian UE |
Apple |
| R2-2009722 |
Need of resource allocation enhancements for sidelink mode 2 |
Ericsson |
| R2-2009834 |
Uu and SL DRX impact to resource allocation mode 1 and mode 2 |
vivo |
| R2-2009869 |
Discussion on sidelink resource allocation enhancements in mode2 |
Lenovo, Motorola Mobility |
| R2-2009924 |
Discussion on Reliability and Latency |
Qualcomm Finland RFFE Oy |
| R2-2009992 |
Resource Allocation Enhancements |
Fraunhofer HHI, Fraunhofer IIS |
| R2-2010047 |
Discussion on RAN2 scope for resource allocation enhancement |
Nokia, Nokia Shanghai Bell |
| R2-2010144 |
On Resource Allocation Mode 2 Enhancement for NR Sidelink |
Convida Wireless |
| R2-2010333 |
On SL Resource allocation enhancements |
MediaTek Inc. |
| R2-2010583 |
Inter-UE coordination for NR V2X |
LG Electronics Inc. |
| R2-2010587 |
Power efficient resource allocation |
LG Electronics Inc. |
| 8.15.4 |
Other |
|
| R2-2008830 |
Discussion on geo-area confinement for non-ITS sidelink band |
OPPO |
| R2-2008852 |
Sidelink Operation Using Non-ITS Band in a Pre-defined
Geographic Area |
CATT |
| R2-2009135 |
Geographic Location based Frequency Resource Operation for NR Sidelink |
Fujitsu |
| R2-2009294 |
SL operation confined to a predetermined geo-area |
Samsung Research America |
| R2-2009412 |
Discussion on WI objective 5: confining sidelink operation to a predetermined geographic area(s) for a given frequency range |
Huawei, HiSilicon |
| R2-2009529 |
Discussion on Geographical area restriction for NR SL |
Apple |
| R2-2009835 |
Mechanism to support confined sidelink operation |
vivo |
| R2-2009866 |
Views on Predetermined geographic area(s) for sidelink |
Lenovo, Motorola Mobility |
| R2-2009937 |
UE Tx Profile |
Qualcomm Finland RFFE Oy |
| R2-2010059 |
Discussion on Simultaneous mode 1 and mode 2 operation and LCP enhancements |
Nokia, Nokia Shanghai Bell |
| R2-2010633 |
Geographic-Area restriction on SL operation |
MediaTek Inc. |
| R2-2010960 |
LS on geo-area confinement |
RAN2 |
| 8.16 |
NR R17 Other |
|
| R2-2010128 |
Periodic SRS in SCell dormant BWP |
Qualcomm Incorporated |
| R2-2010133 |
Introduction of 35 and 45 MHz channel Bandwidths |
T-Mobile USA Inc. |
| R2-2010691 |
LS on questions to RAN WGs on dual Radio UE (2Rx/2Tx or 2Rx/1Tx) support for simultaneous communication with both SNPN and PLMN (S2-2007827; contact: Futurewei) |
SA2 |
| R2-2011064 |
Discussion Summary - [AT112-e][032][NR17] eNPN LS – Phase 2 |
Futurewei |
| R2-2011065 |
Draft LS response on questions to RAN WGs on dual Radio UE support for simultaneous communication with both SNPN and PLMN |
Futurewei |
| R2-2011226 |
Draft LS response on questions to RAN WGs on dual Radio UE support for simultaneous communication with both SNPN and PLMN |
Futurewei |
| R2-2011270 |
Reply LS on questions to RAN WGs on dual Radio UE (2Rx/2Tx or 2Rx/1Tx) support for simultaneous communication with both SNPN and PLMN |
RAN2 |
| 9.1.1 |
Organizational |
|
| R2-2010911 |
RAN2 agreements for Rel-17 NB-IoT and LTE-MTC |
Document Rapporteur (Ericsson) |
| 9.1.2 |
NB-IoT neighbor cell measurements and corresponding measurement triggering before RLF |
|
| R2-2008937 |
Impact on Static devices |
THALES |
| R2-2009058 |
Further consideration on measurement in connected mode |
ZTE Corporation, Sanechips |
| R2-2009146 |
Discussion on the corresponding measurement before RLF |
Spreadtrum Communications |
| R2-2009268 |
Enhancements for Re-establishment time reduction |
Nokia, Nokia Shanghai Bell |
| R2-2009731 |
Neighbour cell measurements in RRC_CONNECTED |
Huawei, HiSilicon |
| R2-2009788 |
Report for [Post111-e][923][NBIOT R17] RLF Enhancements (Qualcomm) |
Qualcomm Incorporated |
| R2-2009789 |
Way forward for connected mode neighbour cell measurement in NB-IoT |
Qualcomm Incorporated |
| R2-2009876 |
Neighbor cell measurements triggering before RLF |
Lenovo, Motorola Mobility |
| R2-2010076 |
Reducing time taken for reestablishment procedures in NB-IoT |
Ericsson |
| R2-2010249 |
Discussion on Total Interruption Time |
ETRI |
| R2-2010460 |
Measurement before radio link failure |
MediaTek Inc. |
| R2-2010905 |
[draft] LS on NB-IoT connected mode neighbour cell measurements |
Qualcomm |
| 9.1.3 |
NB-IoT carrier selection based on the coverage level, and associated carrier specific configuration |
|
| R2-2009059 |
Further consideration on multi carriers configuration and selection |
ZTE Corporation, Sanechips |
| R2-2009147 |
Discussion on enhanced paging carrier selection and multi carrier configuration |
Spreadtrum Communications |
| R2-2009180 |
NB-IoT carrier selection and configuration based on coverage level |
Ericsson |
| R2-2009269 |
Analysis on carrier selection options for NB-IoT |
Nokia, Nokia Shanghai Bell |
| R2-2009732 |
Paging carrier selection based on CEL and on DRX |
Huawei, HiSilicon |
| R2-2009790 |
Support for NB-IoT carrier selection based on the coverage level |
Qualcomm Incorporated |
| R2-2010077 |
NB-IoT carrier selection and configuration based on coverage level |
Ericsson |
| R2-2010470 |
Carrier selection enhancement |
MediaTek Inc. |
| R2-2010906 |
[AT112-e][302][NBIOT R17] Carrier selection (Ericsson) |
Ericsson |
| 9.2.1 |
Scenarios |
|
| R2-2008883 |
IoT NTN scenarios and UE density |
Eutelsat S.A. |
| R2-2008975 |
Email summary discussion on NTN Scenarios applicable to NB-IoT/eMTC |
Eutelsat S.A. |
| R2-2009071 |
Consideration on the scenarios for IoT over NTN |
ZTE Corporation, Sanechips |
| R2-2009114 |
Discussion on scenarios for NB-IoT and eMTC in NTN |
OPPO |
| R2-2009267 |
oOn NB-IoT/eMTC for NTN scenarios and Performance requirements |
Nokia, Nokia Shanghai Bell |
| R2-2009449 |
Scenarios and assumption for IoT NTN |
Qualcomm Inc |
| R2-2009589 |
Discussion on scenarios for NB-IoT and eMTC NTN |
Xiaomi |
| R2-2010237 |
NTN IoT scope, scenarios, architecture, and requirements |
Ericsson |
| R2-2010287 |
Discussion on NTN scenarios for NB-IoT |
Huawei, HiSilicon |
| 9.2.2 |
Applicability of TR 38.821 |
|
| R2-2008899 |
On User-Plane Timers in NB-IoT based NTN |
MediaTek Inc. |
| R2-2008900 |
On Disabling HARQ in NB-IoT based NTN |
MediaTek Inc. |
| R2-2009072 |
Consideration on the applicability of NR NTN to IoT over NTN |
ZTE Corporation, Sanechips |
| R2-2009113 |
Discussion on NB-Io/eMTC support for NTN |
OPPO |
| R2-2009450 |
Applicability of NR NTN SI and WI solutions |
Qualcomm Inc |
| R2-2009591 |
Initial discussion on NB-IoT and eMTC NTN |
Xiaomi |
| R2-2009593 |
Initial discussion on NB-IoT and eMTC NTN |
Xiaomi |
| R2-2009988 |
IoT features and applicability of NR NTN solutions for IoT over NTN |
Nokia, Nokia Shanghai Bell |
| R2-2010247 |
Applicability of NR NTN to NB-IoT/LTE-M UEs that support NTN |
Ericsson |
| R2-2010288 |
Discussion on applicability of TR 38.821 to NTN NB-IoT |
Huawei, HiSilicon |
| R2-2011228 |
[IoT-NTN] Applicability of TR 38.821 on eMTC/NB-IoT based NTN (MediaTek) |
MediaTek |
| R2-2011275 |
[IoT-NTN] Applicability of TR 38.821 on eMTC/NB-IoT based NTN (MediaTek) |
MediaTek |
| 10.1 |
Session on LTE legacy, Mobility, DCCA, Multi-SIM and RAN slicing |
|
| R2-2010701 |
Report from session on LTE legacy, Mobility, DCCA, Multi-SIM and RAN slicing |
Vice Chairman (Nokia) |
| 10.2 |
Session on R16 eMIMO, CLI, PRN, RACS and R17 NTN and RedCap |
|
| R2-2010702 |
Report from Break-Out Session on R16 eMIMO, CLI, PRN, RACS and R17 NTN and RedCap |
Vice Chairman (ZTE) |
| 10.3 |
Session on eMTC |
|
| R2-2010703 |
Report eMTC breakout session |
Session chair (Ericsson) |
| 10.4 |
Session on NR-U, Power Savings, NTN and 2-step RACH |
|
| R2-2010704 |
Session minutes for NR-U, Power Savings, NTN and 2-step RACH |
Session chair (InterDigital) |
| 10.5 |
Session on positioning and sidelink relay |
|
| R2-2010705 |
Report from session on positioning and sidelink relay |
Session chair (MediaTek) |
| 10.6 |
Session on SON/MDT |
|
| R2-2010706 |
Report from SOM/MDT session |
Session chair (CMCC) |
| 10.7 |
Session on NB-IoT |
|
| R2-2010707 |
Report NB-IoT breakout session |
Session chair (Huawei) |
| 10.8 |
Session on LTE V2X and NR V2X |
|
| R2-2010708 |
Report from session on LTE V2X and NR V2X |
Session chair (Samsung) |